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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to state that it's destructive. It adds useful behavioral context by explaining that the id should come from `list_tasks`, which helps the agent understand the workflow dependency. This goes beyond what annotations provide.

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, focused sentence that immediately states the action and resource, then provides a brief hint on obtaining the id. There is no fluff, making it highly concise and well-structured.

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 simple delete operation with no output schema, the description is fairly complete. It covers the core action and id acquisition, but does not explicitly mention the board_id dependency. However, board_id is a required parameter and can be inferred from the board context, and the overall complexity is low, so a 4 is reasonable.

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 input schema has only 33% description coverage, with id and board_id lacking descriptions. The description only clarifies the id parameter by instructing to get it from `list_tasks`, but board_id remains unexplained. Given the low coverage, the description should compensate more but fails to address board_id, so a score of 2 is appropriate.

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 clearly states the action (delete) and resource (task/card by id), and distinguishes it from sibling tools like create_task, update_task, and list_tasks. It also provides a direct pointer to where to obtain the required id, which uniquely identifies the tool's purpose.

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?

The description tells the agent to get the id from `list_tasks`, which is a clear prerequisite for usage. It doesn't explicitly mention when not to use it or alternatives, but the purpose is straightforward and the context of needing to list tasks first is valuable enough to warrant a 4.

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