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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds behavioral context beyond these: it reveals a dependency on other tools for id acquisition and describes the output contents (including paste-ready text). No contradictions exist; the added detail is useful and non-redundant.

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, efficient sentence that front-loads the core purpose, lists the output components, and adds the id source without extraneous words. Every clause earns its place, making it highly scannable for an agent.

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 there is no output schema, the description adequately enumerates the return fields. It also covers the dependency on other tools. It does not mention the optional source parameter, but the schema already documents that. Minor omissions like error cases or rate limits are not critical for a read-only, idempotent get-by-id operation, so the description is sufficiently complete.

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 only 50%: the deckId parameter has no schema description, while source has a description. The tool description compensates for deckId by explicitly stating that ids come from get_archetype and buildable_meta_decks, giving the agent a clear source for valid values. For source, the schema already explains its semantics, so the description adds no new meaning, but overall the gap is adequately addressed.

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 fetches a full tournament decklist by id, enumerates the returned contents (placement, event, price, cards, paste-ready text), and specifies that ids come from get_archetype and buildable_meta_decks. This is a specific verb-resource pairing that distinguishes it from sibling tools like get_archetype or get_meta.

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?

It provides clear context by indicating that deck ids originate from get_archetype and buildable_meta_decks, which tells the agent when this tool is appropriate (after obtaining an id). It does not explicitly state when not to use it or mention alternatives, but the guidance is sufficient for sequencing and selection.

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