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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=false and openWorldHint=false, so safety is covered. The description adds the exclusion behavior, which is useful, but it does not state that the draw is random or that repeated calls return different cards, which is the practical meaning of the non-idempotent hint for an agent.

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?

A single front-loaded sentence with the core action first and the exclusion rule second; no filler, no restatement of the title.

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?

For a five-parameter, fully documented, read-only tool with no output schema, the description covers the action and the exclusion semantics adequately. The remaining gap is the return shape (whether each drawn card includes name, meaning, and reversal state), which the agent must discover at call time.

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 100%, with each of the five parameters documented in the schema including defaults and bounds, so the baseline is 3. The description's only parameter-adjacent content is the meaning of 'exclude', which the schema already spells out as 'Ids of cards already drawn'.

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?

States a specific verb and resource ('draws one or more clarifying cards from the rest of the deck') and adds the exclusion scoping rule. It never names or distinguishes itself from the sibling draw_cards, so an agent must infer the difference between a 'clarifying' draw and a normal draw.

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?

Usage is only implied by the phrase 'from the rest of the deck, leaving out the cards given in exclude', which suggests a follow-up draw after an initial spread. There is no explicit statement of when to pick this over draw_cards, nor any precondition such as supplying previously drawn card ids.

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