Delete 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. The word "delete" signals a destructive mutation, but it does not state consequences, reversibility, permission requirements, or effects on related entities. This is minimally transparent but significantly under-discloses.

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?

"Delete a card." is short, but this is under-specification rather than appropriate conciseness. The one-line description spends its only sentence repeating the tool name instead of providing useful, structured information.

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 the absence of annotations, the existence of many sibling delete tools, and the need to understand deletion implications, this description is far below minimum viable. It lacks usage context, behavioral details, and parameter clarification, making it nearly useless for correct tool selection and 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 description coverage is 0%, and the description adds no meaning to the single required parameter. The schema defines only an id, but the description does not explain what the id identifies or how it is used, so an agent gets no additional semantic value.

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 "Delete a card." is a tautology that simply restates the tool name and title. It names the verb and resource but provides no detail that would distinguish it from sibling delete tools like delete_project, delete_board, or delete_list.

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, no mention of prerequisites, and no reference to related sibling tools. The description gives no contextual cues to help an agent decide between delete_card and other delete operations.

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