get_matchup

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

No annotations are provided, so the description carries the full burden. It discloses the output content (favored, why, tension, priorities) but lacks details on data source, computation method, or limitations. It does not contradict annotations (none present).

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 a single clear sentence that conveys the core functionality. It is appropriately front-loaded but could be slightly more structured (e.g., separating output description).

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?

Given the simple input (two strings) and no output schema, the description provides a good overview of what the tool returns. It covers the main aspects (favored side, reason, tension, priorities), which is adequate for the tool's complexity.

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 coverage is 100% with clear parameter descriptions. The description adds value beyond the schema by explaining the type of analysis (theoretical) and the aspects covered (favor, tension, priorities), which helps the agent understand the output semantics.

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: getting theoretical matchup dynamics between two Hearthstone archetypes. It specifies what it explains (favor, reason, tension, priorities) and distinguishes from siblings like 'analyze_deck' and 'get_archetype'.

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 implies the tool should be used when analyzing archetype matchups, but it does not explicitly state when to use it over alternatives like 'analyze_deck' or 'get_archetype', nor does it provide exclusions or prerequisites.

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