• Be sure to join the discussion on our discord at: Discord.gg/serebii
  • If you're still waiting for the e-mail, be sure to check your junk/spam e-mail folders

About descripting....


Active Member
When we start our fan fic, especially when we're focusing on a Pokemon world, where there's no human in it, do we really have to put some descriptions about the Pokemon that we're going to introduce? Or just state its name and voila?

Coz I've seen a numbers of fan fics that put descriptions for the Pokemon they're referring, but isn't it tiring to describe everything for to introduce every character you make in the story?

On the other hand, will it make some readers confused about what Pokemon we're talking about in the story if we don't use the descriptions?



Don Ledianni
It's best to describe the pokemon and the world around it. Describing things should allow for the reader to get a clear image of what's going on and the scenery. For example:

The scaly purple ekans slithered its way through the tall grass.

Don't state the name. You must describe so we the reader knows what's going on. It isn't tiring. It's just common sense because as a writer you need to show and tell us what's going on in the story. A picture has to be painted in the reader's mind. We may know about the pokemon but we want it described in your own words. That's what a writer has to do.

If you don't then yes. People will be confused.



Fanfiction Critic
The thing is, with description, that it's not there just because people might now know what something looks like, but to describe what is going on and pull a reader into the story. Proper description can fascinate, interest, and hook a reader into wanting to read more.

It doesn't really matter if they know what the pokémon looks like, or not, because you're painting a picture for someone. Would you ignore all things the person already knows about when sharing a story with someone? Would you edit out all the trees, the grass, the sky, the clouds, everything that someone already knows?

Description is one of the most important parts of any story, because without it you might confuse, bore, or even annoy someone. ^^

The Big Al

I just keeping Octo
It's kind of like the isue with the fic I'm writing. It's not Pokemon but it has several races that resemble animals. So it's not enough to name the species since people wouldn't know what you're talking about.

Instead of saying "The Doggel glided past".
It's more like "The sky blue furred, spaniel like Doggel glided by using her long ears like wings to stay aloft."

Description is always good.


Just me
It's not necessary, and by all means don't stop every time a Pokémon appears in your story to spend a paragraph describing it in excruciating detail, but description is nice for padding out your subsequent sentences involving said Pokémon and making them more vivid and interesting.


Lost but Seeking
Warning! tl;dr off the forward bow!

The thing with description is that it has to serve a purpose. Description is a tool that writers use to highlight things of note or to influence the atmosphere of a piece. Typically, if something is described in-depth, it's the author doing the equivalent of saying, "Hey, look here! This is important! Pay attention!"

The problem is, that when many people talk about "describing pokémon," they're talking about giving a blow-by-blow on a pokémon's physical makeup. This would be appropriate in some situations, but in general it isn't, and here's why: the character in any pokémon 'fic would be expected to be familiar with his world's native fauna, and therefore he or she wouldn't give any passing pokémon more than a cursory glance. If there was something unusual about a pokémon's appearance, they might notice it; otherwise, they're not going to dwell on the physical characteristics of the beast unless they've decided they need to inspect it for some reason.

Description is very important. Description in the terms of what most people on these boards consider it to be--talking about what something looks like in detail--is often not, and indeed can be quite a hindrance to a reader's understanding and enjoyment. Let's have a couple of examples. This is the sort of thing that most people seem to mean when they talk about "describing pokémon":

The gecko-like creature stood about three feet tall, and its body was covered in a layer of fine, glimmering green scales. A long, tapering leaf sprouted from the back of its head, and further leaves adorned its wrists and rump. Its underbelly was a striking ruby hue, and its eyes were yellow.

This, as I hope even the people who advocate such "description of pokémon" would tell you, is an absolutely sucky passage. They'd say (or at least, I hope they would), that the pokémon shouldn't just be standing there while the narrator discusses its physical characteristics; that's boring, and it wrenches the reader out of the flow of the story in order so that the narrator can drone for a few sentences about grovyle before diving back into the action.

And it gets worse! Sometimes, overzealous writers will go so overboard in talking about a pokémon that you won't even be able to tell what it is when they're done with it! Observe:

The creature was bipedal and stocky, with thick, powerful paws banded with heavy black rings. A layer of thin, fuchsia fur covered its vaguely pear-shaped form, and two beady black eyes stared out from its squashed face, which was framed by floppy ears like isosceles triangles with the tops cut off. Jutting lower teeth, the same strange purple, overtopped another heavy black ring about the creature's neck.
I'll admit to being far worse at obfuscation than many of the authors here, but I hope you'll see my point in that this "description" is puzzling rather than helpful when it comes to determining a pokémon's species.

So what is "good" description, then? Well, what if the author wants to talk about what a pokémon looks like but doesn't just sit there and list qualities of it--or at least, doesn't make the listing so blatant?

The gecko-like creature hissed, showing tiny teeth like a forest of little razors. Its yellow eyes flicked between the travelers, and then it leaped from the branch overhead, flaring the leaves on its wrists as it soared across to the tree opposite. Jerry caught a flash of brilliant red underbelly as the pokémon passed overhead, the leaf on its head streaming in the wind, before it hit the far tree trunk with a heavy thump and clung on with its fingers and toes. It scuttled up the side of the tree a couple of feet before vanishing into a cluster of foliage, its green scales blending perfectly with the leaves.

There are times when such a passage might be appropriate if one wanted to introduce a grovyle to one's 'fic. However, remember that every word in a piece of writing should ideally serve a purpose, and those that don't should get cut. Description is all about conveying information--telling the reader what is important, guiding them to see what you want them to see in a particular passage. Let's have a look at what our two examples thus far tell us before seeing one more, what I would call the "correct" way to describe a pokémon.

First, our list-y description. What point does it eventually get across? That the pokémon we're looking at is a grovyle. Also apparently one that's sitting still and doing nothing while the narrator considers its virtues, but that's already been covered.

The description above is a little more complex. The reader should, hopefully, still get that, "Oh, that's a grovyle!" The passage does a little more than that, though. It lets us know that the grovyle's hostile towards humans, or at least towards this "Jerry"--at the least, it doesn't seem too friendly, even if it doesn't outright attack him. It also establishes a sort of wild, feral atmosphere. Grovyle is canonically an extremely rare pokémon, so one would imagine that Jerry must be deep in the wilderness, perhaps even somewhere unexplored, if he's going to be encountering grovyle in their natural habitat.

Before I tie all this together, let's see how I think people should go about describing pokémon:

The grovyle tilted its head to the side and chirped, yellow eyes inquisitive. Its scales were scuffed and hidden here and there under patches of mud and dust, and there was an irregular bite taken out of the leaf on its head, but though its crooked grin showed a few missing teeth, grin it did, and if it had had a tail, Jerry had the feeling it would be wagging like mad.

Now, again, let's examine what this passage conveys. First of all, yes, it's a grovyle--though here it's actually just named, which immediately conjures up a complete grovyle image in the mind of the reader. Moreso than that, though, it's a grovyle that's apparently fallen on some rough times. It's got a bite taken out of the leaf on its head and it's a bit dirty, not to mention that it's got a few holes in its smile. Moreso than that, though, this passage gives you a fair amount of insight into the grovyle's personality, or at least what it's projecting to Jerry as its personality. It's definitely friendly, and its manner also seems a bit inquisitive, perhaps even slightly eccentric--its smile is described as "crooked," for example, and it seems to be acting a little odd for a grovyle; it even reminds Jerry of a dog, to some extent, which brings on further connotations of playfulness, loyalty, and so on.

That's a lot, coming from so short a passage. What's more, it reveals more than just what the pokémon looks like, and instead focuses more on the way it behaves. By calling the pokémon a "grovyle," the text immediately gives the reader a basic idea of what to work with, then goes about describing ways in which this particular grovyle is different than others, rather than rehashing what the readers--or at least the story's protagonist--already know and wouldn't ordinarily think about, instead considering the archetypal image of a grovyle that they have already acquired through exposure to canon.

This is why professional authors, or at least the good ones, can often get away without giving a blow-by-blow description of their character's physical appearance. In fact, the really good ones can do so so subtly that the reader never realizes that the image they have of that person in their head is constructed almost entirely from elements of that character's personality that their brain has associated with particular physical traits. This is because what a character looks like usually isn't important--rather, it's who they are that is the concern of the reader. You don't sympathize with a character because they have the same color eyes as you do, but rather because you feel connected with that character through their emotions and personality traits.

Therefore, physical description is usually only used in order to "point out" elements of a character's personality. A person's hair color could be described, but usually only if it somehow relates to an underlying theme of the novel that plays off color to an extent or to draw on our understanding of the connotations different hair colors usually have for a character's personality. Consider, though, what you might be able to tell about a character given their hairstyle. What if their hair was messy and unkempt? What if it was done up in a style that was popular twenty years ago? What would you decide about their character then?

Thus, character description is usually less about getting at the "what" than it is about getting at the "who."

But what about my saying that the second grovyle passage was okay "in some cases?" That talks almost exclusively about the pokémon's physical appearance, so why is it okay?

Because the purpose of that passage is NOT to describe the grovyle. Instead, the information it presents says more about the human character, Jerry, than it does about the beast itself (besides what was already noted). But how is that possible, given that the entire passage is about the grovyle, and the (presumably) human character is identified only briefly and by name?

First of all, it suggests that he might be unfamiliar with grovyle. Think about it. When you see a lizard, are you thinking to yourself, "Oh, it's a small, scaly quadruped with a long, slender tail. It has eyes on the sides of its head and clawed feet. It's blue with black spots." Probably not, unless you've never seen a lizard before in your life. Upon registering the creature, you're instead going to think, "Oh, it's a blue lizard with black spots."

The care with which the grovyle's physical appearance is detailed in the passage suggests that Jerry is trying to figure out what it is. Instead of immediately jumping to grovyle, his mind is listing down notable traits and starting to cross-reference them with his knowledge of other species--geckos, perhaps. And, because this is the pokémon world, his unfamiliarity suggests several things--perhaps that this is an alternate universe fiction, where many of the pokémon species with which we're familiar are unknown. Perhaps Jerry lives somewhere cut off from the majority of the world, where grovyle is a fairly well-recognized species. Maybe he just slept through most of his biology/pokémonology classes and doesn't pay much attention to stuff about pokémon. For one reason or another, his mind doesn't skip immediately to "grovyle" when he sees one, and the narrator therefore has to point out details that will make us think "grovyle," even if Jerry doesn't.

There's another possible explanation, too. If you've ever had a cat suddenly dart out from the bushes next to you and run across your path, you'll probably have experienced a reaction similar to, "Small furry very fast thing dark-colored doesn't look like it's coming at me--oh, okay, it's just a cat." Fear is great at sharpening the senses, and when we're startled our brains usually run into overdrive, picking up all the details about something that we might otherwise just glance at and dismiss as unimportant. If Jerry were just surprised by the grovyle, it would probably take him a couple of seconds to realize what it actually was, as the passage makes it sound like it was moving relatively fast, and for a moment his brain would just be pulling in data, not synthesizing it. If that were the case, the next paragraph would probably start with some comment referring to that creature as a grovyle, rather than being a paragraph in which Jerry considers that "weird thing" he saw up in the trees. This would convey the fact that he's on edge, wary, and uncertain in this environment. The description of the grovyle, therefore, isn't so much important because it tells the reader that the pokémon is a grovyle, but because it helps to convey the skittish nature of the protagonist, as well as, perhaps, let the reader feel a little bit of his unease. It's primarily atmosphere, and perhaps a little characterization for Jerry, depending on the circumstances, that this descriptive passage serves to illuminate.

So, that paragraph could be saying a lot--but relatively little of it has to do with the grovyle itself! In fact, the pokémon itself is probably unimportant, and if it does end up returning for any reason, it will probably receive further description detailing its purpose in the story.

In the end, I would encourage you to describe pokémon. In fact, I would say that it's vital, even if you don't treat them as human-like characters; the fact that they're not being treated like beings with human intelligence, after all, is just the sort of thing you need to get at through a description of the creature's behavior. But please, don't sit there and describe what color a pokémon is and what, in general, it looks like, unless this is somehow unusual or otherwise furthers the story in one way or another. It's perfectly kosher to just say, "The trainer had a magneton," if there's nothing remarkable about said pokémon.


Active Member
*thinking* So like you guys were saying, I should (firstly) name the species of the Pokemon then described in order for the reader to be able to picture that Pokemon in their heads?

Good point, actually. I haven't thought of that ^^. Thanks for the big help, everyone. It really helps.

Next thing, still in the topic of describing (in case one of the mods were currently viewing this thread to check for any slip-ups in this thread), are prologues necessary for most fan fics?

Coz I read most books like Witch Child and The Bronze Bow, where the authors didn't put any prologues in their stories and jumped instantly into the story, it created a special situation where the readers are in the middle of something and that (obviously) caused a feeling like 'wow, I'm in the middle of the persecution of witches' and 'what's it going to be like'. Here, I've seen several fan fics (don't mind me, I haven't read all fan fics here) that starts their story with prologues, which serves as a purpose so that the readers won't get lost in the story. Is it really true and do we have to put something to lead the readers to what the story's going to be, or could we jsut leave all the interpretations to the them?



Lost but Seeking
Next thing, still in the topic of describing (in case one of the mods were currently viewing this thread to check for any slip-ups in this thread), are prologues necessary for most fan fics?
Probably not for most. Prologues tend to be a chapter that shows events happening significantly before the beginning of the story. They often don't include the protagonist, instead showing events that somehow relate to the story being told but which the protagonist is unaware of--while at the same time you, the author, think it is important that the readers know about in order to set up some dramatic irony. Prologues often introduce the problem with which the protagonist will later need to tangle; they many times focus on the antagonists.

If you don't see the need to introduce your conflict in this way, it would be better for you to simply begin at the beginning, no prologue.


Friendly POKéMON.
Well, many prologues themselves have ceased to explain the actual point of the story to any great degree; they often present to the reader a set of unrecognizable characters and events right off the bat, leaving the carriage of the story to the sense of mystery hopefully generated. If you're beginning the story at the beginning of the main events of the story (if a journey-fic OT begins shortly before the trainer gets a starter, for example) you don't need much of an explanation in the first place, because all the plot details will transpire and be revealed in their own time and right now the reader can base himself firmly in the simple concept of a beginning, with little to infer or to be explained. If, however, you're beginning right in the middle of the action as in the stories you referred to, a fine balance between explanation and mystery should be set; to begin with, it's probably not advisable to explain everything, as that would overload the reader with information that means little to him at the moment, but some fact or character should be established, with mentions to a few different unknown things, so that the reader can get a bite-sized feel of the story while knowing that there is a lot more to be understood.

In the end, a prologue is simply a standard introduction to the story. You can use it for a few explanations if that seems appropriate, and if you want to give it a miss for the sake of some special style of your own, this is fine too as long as it serves your style well.

Just a little contribution to the first question: very importantly, describe a pokémon as you would describe anything else in your world. All the usual devices and instincts you have for describing, say, a room or a field still hold true for pokémon. In something like a forest, describe them as you would animals in a real-life forest: part of the scenery; a Pokémon fanfiction reader here is probably familiar with most of the known pokémon, and does not need to be informed that a pikachu has pointed ears and red cheeks. Everything else that could possibly be important is probably rounded off in Negrek's marvellous reply.


Active Member
Okay, then.

Big thanks to those who post here, you guys really help me alot ^^.

I'll post again when I got other Q's to be answered (xixixi). :D
Um, just so you know, there's a Fan Fic Q and A thread (which I think should be stickied) so you don't have to create a new thread everytime you have a question.


Active Member
Well, I mean I'll still post Q's in this thread.

Talking about that Fan Fic Q's n A's, where's that thread located?


Really and truly
If the name of the thread is "About description," then the thread shouldn't be used for topics other than that. As mentioned, if you use the SPPf Search function, you can find the Q&A thread where you can post your smaller questions, though.

However, I think that this thread is really great; for some reason, we writers of SPPf have always been obsessed with description. In fact at one point, every fic review you'd see usually contained something along the lines of "add more description" and it was some sort of fad.

I myself have always been fascinated by description, and think it's a pretty broad topic. Negrek did a wonderful job explaining it, and I think she really hit the nail on the head, but I'm leaving this topic open so anyone else who wants to can post their thoughts/opinions on description.

My summed-up take: nobody is going to be confused if you don't tell us what a Mudkip looks like, and if a Pokémon only appears for a few seconds then you don't need an in-depth description of it - like if the character sees a Pidgey in a tree, we don't need to be told every little detail. A beige and tan-feathered bird sat quietly, digging its tiny pink talons into the tree branch is perfect.

As with most things, when you describe a Pokémon with a greater importance to the story, again, don't go overboard, but try to incorporate actions into the description. If it's a Ponyta, describe its black hooves clopping against concrete and fiery mane blowing in the wind, show the sunlight glancing off a Seviper's night-black scales as it slithers along the ground, or a Flygon whipping its green-striped tail through the air as it tosses its pointed head with its long green horns defiantly. Again, as Negrek said, try to give signs of their personality, or the way they're perceived, through their actions, even during the description itself. Describing an Eevee's long ears drooping and bright eyes downcast glumly really says more than "the Eevee had long ears and bright eyes. It was sad" because it paints the picture of that Eevee in the reader's mind.

Besides, a long paragraph that just lists attributes like a shopping list is only going to bore the reader. If you're going to describe a Pokémon, keep it relatively short and simple, and don't go into every little detail. If it appears again later, you can always go over bits again. ^^


Ryano Ra

Verdant Vitality
^.^; Negrek pretty much said it.

I wouldn't get discouraged to describe pokemon, I would go for it, but not the extent of listing all of its details in a paragraph. It would be very best to basically incorporate a pokemon's appearance with the current events that's going on in the chapter, such Negrek provided in her examples. Otherwise, it would get boring and tedious, and would bore people. Description is a very hard mechanism to function, but when functioned appropriately, it can be an extremely powerful aspect of your story. ^^


Active Member
2 Psychic: Thanks^^! Yeah, I know it's a bit run-off based on the topic of the thread, but I'll try my best to get used to it. Thanks for the advice! I'm thinking about writing a fan fic but I'm not sure how it will go on, so I'll need as much advice as possible to help me with it.

2 Ryano Ra: Thanks! I agree with that. Sometimes I got a bit carried off in writing essays so my writings kinda longer than anybody else. Yup, I'll practise on descripting and thanks again for the advice^^

Yup, Negrek had been a really great help here, but I'll appreciate anyone who wants to express their ideas here.

Anymore ideas, anyone?

Ryano Ra

Verdant Vitality
2 Psychic: Thanks^^! Yeah, I know it's a bit run-off based on the topic of the thread, but I'll try my best to get used to it. Thanks for the advice! I'm thinking about writing a fan fic but I'm not sure how it will go on, so I'll need as much advice as possible to help me with it.

2 Ryano Ra: Thanks! I agree with that. Sometimes I got a bit carried off in writing essays so my writings kinda longer than anybody else. Yup, I'll practise on descripting and thanks again for the advice^^

Yup, Negrek had been a really great help here, but I'll appreciate anyone who wants to express their ideas here.

Anymore ideas, anyone?
No problem. ^^ If you need any additional help, just PM me sometime, and I'll be very glad to assist you in terms of description.