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

Annotations only declare the safety profile (not read-only, not destructive, not idempotent), so the description carries real weight here and delivers: the refusal lands on the lead's timeline, the next run reads it, and stop-words 'pause the lead' — an outward side effect beyond the card itself. It stops short of saying what happens to the card's own state or whether the refusal is reversible.

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 action and its two payloads are front-loaded, which is good. However, transcribing all 26 enum values back into prose largely duplicates the schema's enum and bloats the description, so not every token earns its place.

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?

With no output schema, the description usefully covers the downstream consequence (timeline placement, next run consumption) and the semantics of both non-id parameters. It omits what the response returns and whether the card can be brought back, but for a single-card mutation with annotations covering safety it is close to sufficient.

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 coverage is only 33% (words has no schema description), and the description compensates by explaining that 'words are read too', that named dates/events are waited for, and that stop-words pause the lead. The reason_code enumeration duplicates the schema enum but frames it as the required 'why', adding intent to an otherwise bare enum.

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 ('Refuse') and resource ('a card') plus the required reason_code payload, so the core action is unmistakable. It does not, however, differentiate itself from the very similar siblings approve_a_card, set_a_card_aside, stop_a_card, or bring_a_card_back, which an agent must disambiguate on its own.

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?

There is no when-to-use guidance and no named alternative. With siblings like approve_a_card, set_a_card_aside, bring_a_card_back, and stop_a_card all operating on cards, the description never says which condition selects refusal over setting aside or stopping. Usage must be inferred entirely from the tool name.

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