delete_card

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions 'Returns: The Trello API response confirming the deletion,' but does not state that deletion is permanent, irreversible, or may fail for nonexistent IDs, and it does not mention permission requirements.

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 compact and well-structured with a leading sentence, Args block, and Returns block. No redundant text appears; every sentence contributes to understanding the tool.

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?

For a one-parameter mutation tool with an output schema, the description covers the core essentials: action, parameter, and return value. However, it lacks any warning about the destructive/permanent nature of deletion, which would be important for an agent to weigh before invocation.

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 0%, so the description must explain the parameter. The line 'id: The Trello card ID to delete' provides clear semantic meaning beyond the schema's bare string type, fully covering the only parameter.

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 opens with 'Delete a Trello card,' a clear verb+resource statement that unambiguously identifies the operation. Among siblings (create_list, create_card, search, create_board, delete_board), this is distinct and self-explanatory.

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 is given about when to use this tool versus alternatives. It does not state prerequisites, such as needing an existing card ID, nor does it distinguish itself from delete_board or other destructive tools.

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