WoW Character Summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the tool's safety profile. The description does not disclose any additional behavioral traits such as rate limits, authentication requirements, or edge-case behaviors, but it does not contradict the annotations.

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 concise and well-structured: a one-sentence summary of what the tool does, followed by clear Args and Returns sections. Every sentence provides value, with 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 is complete for a simple read tool with two parameters: it lists the returned profile fields, explains parameter formats, and points to related tools for more details. The existence of an output schema and annotations further reduces the need for the description to explain return structures or safety.

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?

With schema description coverage at 0%, the description takes on the responsibility of explaining parameters. It adds concrete meaning by giving examples for realm ('Twisting Nether' or 'twisting-nether') and specifying that character is case-insensitive, going beyond the bare schema.

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 the tool's purpose: 'Get the headline profile for a character' and enumerates the specific fields returned (level, class, spec, race, etc.). It distinguishes itself from sibling tools by naming alternatives for gear and Mythic+ detail.

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 description provides explicit usage guidance by instructing to 'Call wow_character_equipment or wow_character_mythic_keystone for gear and Mythic+ detail,' which clearly differentiates when to use this tool versus its siblings. It also gives parameter usage examples for realm and notes character names are case-insensitive.

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