suspend_card

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

Discloses reversibility, non-destructiveness, retention of history and schedule, and return format. No annotations exist, so description compensates well, though minor details like behavior on already-suspended cards omitted.

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?

Two sentences, front-loaded with action and key details. No wasted words.

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 simplicity (1 param, no annotations), description covers purpose, usage, behavior, return format fully. Output schema exists but description already provides key return info.

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?

Only one parameter (card_id), self-explanatory from context. Schema coverage is 0%, but the parameter is trivial and description doesn't add extra semantics beyond obvious.

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?

Clearly defines the tool as shelving a card, keeping history and schedule but removing from due queue. Distinguishes from siblings like delete_card and unsuspend_card.

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?

Explicitly states it is a reversible, non-destructive alternative to delete_card for uncertain cards, providing clear when-to-use guidance.

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