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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds two useful behavioral facts beyond that: reproducibility via seed and a 10-credit (Tier 1) cost. It says nothing about reversal behavior (allowReversed default true) or response shape, so the added value is moderate.

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?

Front-loaded with the core action in one sentence, followed by a compact seed note and group/cost tags. No filler; appropriately sized for a simple single-draw tool.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. However, with 5 parameters and only 40% schema coverage, the unexplained 'question' and 'allowReversed' parameters leave the definition short of complete for correct invocation.

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 40%, so several parameters (question, allowReversed, seed) are undocumented in the schema. The description compensates for seed only ('deterministic shuffle') and leaves question and allowReversed unexplained, giving partial coverage of a below-50% base.

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 states a specific verb+resource ('Draw 1 card from the RWS deck') and the title reinforces the single-card scope, which distinguishes it from multi-card siblings like draw_three_card or draw_celtic_cross. It stops short of naming an alternative redirect, so no explicit sibling differentiation.

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 only usage-like guidance is 'Optional seed for deterministic shuffle,' which explains one parameter rather than when to choose this tool over the many other RWS/Marseille/Lenormand draw tools. No when-to-use, when-not, or alternative routing is provided.

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