delete_task_attachment

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

Describes ID resolution behavior (task_id resolved to UUID) and that att_id is passed through. No annotations, so description carries burden. Could mention irreversibility, but sufficient for understanding.

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?

Two front-loaded sentences with no waste. Every sentence adds distinct value: purpose and ID resolution details.

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?

Covers input parameters well. No output schema shown but presumably available; description doesn't need to explain return values. Missing potential error conditions, but acceptable for a simple delete operation.

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?

With 0% schema coverage, description adds critical meaning: explains accepted reference forms for task_id and clarifies that att_id is an attachment id (not item ref). Significantly beyond type info.

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?

Clearly states it deletes a single attachment from a task. Differentiates from siblings that delete other entities like tasks or comments.

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?

Specifies the action and the context (delete attachment from task). Provides guidance on ID formats for task_id. No explicit when-not-to-use but clear from name and description.

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