kaiten_archive_card

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal the key behavior — setting the card condition to archived — but it does not mention whether the operation is reversible, what permissions are required, or what side effects occur. Core behavior is clear; broader consequences are not.

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 description is a single compact sentence with a useful clarifying parenthetical. It is front-loaded with the action and contains no filler or redundant detail.

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?

The tool is simple with only one parameter, so the description is nearly adequate. However, with no annotations and no output schema, the description leaves the agent to infer success/error behavior and whether archiving can be undone. A short note on reversibility or expected outcome would make it complete.

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 single parameter card_id is already fully described in the schema as 'Card ID or key' and is required. Schema description coverage is 100%, so the description adds no extra param semantics, but none are necessary here.

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 and object: 'Archive a Kaiten card', and adds a clarifying parenthetical 'set condition to archived' that explains what archiving means. This distinguishes it from related mutations like kaiten_delete_card, kaiten_update_card, and kaiten_move_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?

There is no guidance about when to use this tool versus alternatives such as delete_card or move_card. The intended use is implied by the name and one-line description, but no explicit conditions, exclusions, or alternative recommendations are provided.

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