delete_card

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

No annotations are provided, so the description must disclose behavior. It says 'delete' but adds '(reset / cleanup)' which suggests non-permanent deletion, but this is not elaborated. No mention of consequences, reversibility, or permissions.

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?

Very short, but conciseness is not a virtue when it sacrifices clarity. The structure is front-loaded but lacks sufficient detail for safe agent use.

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?

Although operations with 1 parameter and an output schema could be simple, the description fails to explain return values, side effects, or the precise meaning of '(reset / cleanup)'. This is incomplete for a deletion tool.

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 0%, and the description only says 'by id'. It adds no detail about the card_id parameter beyond what the schema already provides (integer, required). Ambiguity remains about acceptable values.

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?

Description clearly states the verb (Delete), resource (card), and scope (by id). It also distinguishes from sibling tools like edit_card or suspend_card, which have different actions.

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?

No guidance on when to use delete vs. alternatives like suspend_card. The parenthetical '(reset / cleanup)' hints at a specific use case but is ambiguous and not explicitly explained.

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