delete_test_result_attachment

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the scoping fact that the attachment belongs to a test result and says nothing about permanence, permission requirements, or what happens to the parent test result.

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?

A single front-loaded sentence with no filler or redundancy. It is arguably too terse rather than too long, but structurally it is clean and immediately scannable.

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 destructive, non-reversible mutation with no output schema and one undocumented required parameter, the definition leaves important gaps: irreversibility is not restated in prose, the attachmentId semantics are unexplained, and no guidance distinguishes it from sibling delete tools.

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 only 50%: 'id' is documented as the test result UUID, but 'attachmentId' has no schema description at all. The description does not compensate by clarifying that 'id' is the parent test result and 'attachmentId' is the UUID of the attachment to remove, leaving the meaning of the second parameter entirely implicit.

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 states a specific verb and resource ('Delete an attachment') and scopes it to 'from a test result', which differentiates it from the generic delete_attachment and from delete_work_item_attachment. It is clear what the tool does, though it does not name the alternatives explicitly.

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 when-to-use or when-not-to-use guidance is given. With siblings such as delete_attachment, delete_work_item_attachment, and delete_test_result_attachment in the catalog, the definition never says why an agent should pick this variant over the generic attachment deletion.

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