archive_card

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

Discloses that card is hidden but recoverable, which is key. But no annotations exist, so description carries full burden; missing details on permissions, side effects, and recovery process.

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 efficient sentences convey purpose and key behavior. The Args section is redundant with schema but not harmful.

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?

Adequate for a simple tool with one parameter, but lacks error handling, return value (no output schema), and comparison to similar siblings like move_card_to_iteration.

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?

The description adds a format example ('ON-914') for card_ref, which the schema lacks. However, with 0% schema coverage, the minimal example only partially compensates; it doesn't explain where to find the reference.

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 states it archives a card by moving to Archive iteration, distinguishing it from deletion. However, it doesn't fully differentiate from sibling 'move_card_to_iteration'.

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?

Implies usage when you want to hide but keep recoverable, but no explicit alternatives or when-not-to-use provided.

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