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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds useful return-shape context by naming included relations and explaining that `character_variables` is the filled look details in `[{key, value, text}]` form, though it does not cover not-found or permission behavior.

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?

It is a single front-loaded sentence with no filler. The parenthetical is dense but every listed field contributes to understanding what the tool returns.

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?

For a simple one-parameter read tool with no output schema, the description helpfully enumerates the returned fields and nested `character_variables` structure. The main remaining gap is the lack of explanation around `character_uuid` semantics and error behavior.

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?

The schema has zero description coverage for `character_uuid`, and the description never explains that parameter's meaning, required status, or format. The parameter name is self-explanatory, but the description does little to compensate for the schema gap.

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 states a specific verb and resource: it retrieves one character, and it enumerates the full set of included fields. The singular scope and explicit inclusion of `character_variables` distinguish it from `list_characters` and `get_character_variables`.

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?

The singular 'One character' implies this is the full-detail fetch by identifier, contrasting implicitly with list-style siblings. However, it does not explicitly say when to use this versus `list_characters`, `get_character_variables`, or other related read tools.

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