Delete Attachment

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

The description discloses that the action is permanent and returns an empty object {} on success, adding behavioral detail beyond the annotations (destructiveHint, idempotentHint). It does not contradict any annotations.

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?

Three concise sentences, each providing essential information: the action, the return value, and the permanence warning. No wasted words, with the most important information front-loaded.

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 single-parameter delete operation, the description fully covers the core action, result, irreversibility, and how to obtain the required ID. Combined with the annotations and schema, there are no significant gaps.

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 already fully describes the attachment_gid parameter (100% coverage). The description adds value by pointing to asana_get_attachments_for_object as the source for GIDs, enriching the parameter's contextual meaning.

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 'Delete an attachment from a task or project' with a specific verb and resource. It clearly distinguishes from sibling attachment tools like asana_get_attachment and asana_create_attachment_for_object.

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?

It provides clear context by instructing users to obtain attachment GIDs from asana_get_attachments_for_object, which is a prerequisite for using this tool. It does not explicitly discuss alternatives, but the deletion scope is unambiguous given the sibling tool list.

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