Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral detail beyond annotations by listing the returned sections and noting that image URLs are limited to the newest 20 in the gallery; it does not cover missing-character behavior or auth requirements, but those are secondary for this read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core retrieval scope and then lists the included fields efficiently. The enumeration is somewhat long but each item contributes to the agent's understanding of what is returned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description effectively serves as the return-value specification by enumerating the character sections and image URL limit. It is complete for safe read retrieval, though it leaves the character_id input source/format implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, character_id, and schema description coverage is 0%, so the description needs to explain it. The description says the tool retrieves 'one character' but never clarifies where that ID comes from, its expected format, or how to obtain it from find_characters or list results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific retrieval verb and names the exact resource: everything LoreKeeper saved about one character. It enumerates the included sections and image URLs, making the scope clear and distinguishing it from broader search/list tools such as find_characters or image-only tools like get_character_images.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states the use case: describing, voicing, or drawing the character consistently. It does not name when to use an alternative tool or when not to use this one, but the context is clear enough for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.