WoW Character Resource (raw)

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

The description discloses that the response has 'key'/'href' link objects stripped out and warns that 'achievements' and 'statistics' are very large, recommending narrower resources. These are behavioral traits beyond what the annotations (readOnlyHint, idempotentHint) already provide. No contradiction exists.

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 well-structured with Args and Returns sections, uses compact bullet-like lines, and every sentence provides essential information. There is no fluff or repetition of schema fields.

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?

The description fully covers what the tool does, when to use it, parameter semantics, return behavior, and performance caveats. The output schema exists and handles return value structure, so the description need not explain that further. For a generic fallback tool, it is exceptionally complete.

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?

Schema schema description coverage is 0%, so the description compensates by explaining each parameter: realm (name or slug), character (case-insensitive), and resource (allowed sub-resource paths with examples). It also adds context on resource selection, such as preferring narrower resources, which is not evident from the enum alone.

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 clearly states 'Fetch any other character sub-resource that has no dedicated tool,' which is a specific verb (Fetch) and resource (character sub-resource). It also distinguishes itself from dedicated sibling tools like wow_character_summary and wow_character_equipment by specifying it is for resources without a dedicated tool.

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 says to use this tool for sub-resources that have no dedicated tool, and advises 'prefer a narrower resource where one exists.' This provides both when-to-use and when-not-to-use guidance, and implies alternatives (dedicated tools).

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