budget_upgrade

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

Annotations indicate readOnlyHint, idempotentHint, and openWorldHint. The description adds behavioral context by specifying the ranking method (synergy-per-dollar) and external dependencies (EDHREC, Scryfall). No contradiction with 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 extremely concise: two sentences that front-load the purpose and follow with essential detail. Every sentence adds value without redundancy.

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 lacks explicit information about return format or output structure, which is a gap given no output schema. The AI agent may need to infer that suggestions include card names and prices, but this is not stated.

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?

Input schema has full coverage (100% descriptions). The description adds value by explaining the ranking criterion (synergy-per-dollar) and budget ceiling, which complements the schema's parameter descriptions (e.g., 'budget' as 'Maximum price per card in USD').

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: 'Suggest budget-friendly upgrades for a commander deck' and explains it 'Ranks EDHREC staples by synergy-per-dollar within the given budget ceiling.' This distinguishes it from sibling tools like 'evaluate_upgrade' (general upgrades) and 'price_comparison' (price-focused).

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 mentions dependencies: 'Requires EDHREC (for staples) and Scryfall (for prices),' implying when the tool is appropriate. It does not explicitly state when not to use or list alternatives, but the context is clear enough for an AI to decide.

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