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

The description clarifies the *nature* of the analysis (e.g., identifying 'functional categories' and what the deck is 'short on'), adding significant behavioral context beyond the functional safety hints provided in the annotations. It clearly outlines the depth of the AI's inspection.

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 definition is maximally concise. It uses a single, front-loaded paragraph to define the tool's entire value proposition, ensuring that every word contributes to the agent's understanding of the tool's unique capabilities.

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 complexity of analyzing a specialized format like Commander, the definition is highly complete. It covers what is analyzed, the required input format cues, and the nature of the expected output analysis.

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?

The description adds crucial operational meaning to the `decklist` parameter. It clarifies that the tool specifically accepts Commander formatting (e.g., 'Commander heading or *CMDR*'), which is a critical piece of semantic information needed for proper invocation that goes beyond the basic input schema description.

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 is highly specific, clearly stating that the tool analyzes a deck 'whole,' addressing its 'bracket,' 'themes,' and 'functional categories.' This provides a much richer purpose than a generic 'analyze' tag and distinguishes it functionally from other tools like 'card_lookup'.

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?

While it doesn't explicitly name alternative tools like 'card_synergy,' the detailed description of its analytical scope (themes, bracket) implicitly guides the agent to use it for comprehensive high-level assessments. The functional scope clearly defines when it should be used rather than for simple card lookups.

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