WoW Mythic+ Profile

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds beyond that: it notes the 'Returns an error if the character has not completed a Mythic Keystone dungeon in that season' and explains the default season selection, which are useful behavioral details not present in 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 front-loaded with a clear purpose sentence, followed by a structured Args list and a Returns line. It is concise yet covers all necessary details without redundancy, earning each sentence's place.

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 tool has an output schema, so the description doesn't need to detail the return structure. It covers parameter semantics, default behavior, and an error condition. The only slight gap is the lack of explicit guidance on when to select this over sibling tools, but the purpose is sufficiently clear.

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 description coverage is 0%, so the description carries the full burden. The Args section explains each parameter: realm accepts name/slug, character is case-insensitive, and season_id defaults to the most recent season. This fully compensates for the lack of schema descriptions.

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 verb ('Get') and resource ('a character's Mythic+ score and best dungeon runs for a season'), clearly distinguishing it from sibling tools like wow_character_summary or wow_character_equipment. The title 'WoW Mythic+ Profile' reinforces the focus.

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 clearly implies when to use the tool—when Mythic+ score and best runs are needed—and provides context about seasons and defaults. It doesn't explicitly name alternatives, but the sibling tool names and the tool's specific focus make the use-case evident.

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