delete_test_case_attachment

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the mutation semantics are known. The description adds useful specifics beyond that: it clarifies that this permanently removes the file and that both IDs are needed, though it says nothing about auth needs, cascading effects, or recoverability.

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 sentences that restate the same action twice ('Delete an attachment from a test case' then 'Delete a specific attachment from a test case...'), which is mildly redundant. It is front-loaded and short overall, but one sentence could have been cut.

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 tool with annotations covering the safety profile and no output schema, the description covers the essentials: what is deleted, the identifiers required, and that removal is permanent. Only authorization and cascade behavior are left unaddressed.

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 reported at 0%, so the description must carry parameter meaning; it does state that both the test case identifier and attachment identifier are required, which corresponds to the two nested fields. However, it adds no format, type, or constraint detail beyond what the nested schema properties already say.

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?

States a specific verb (Delete) and resource (attachment from a test case) with the scope clarified as a single attachment identified by both test case and attachment IDs. This clearly distinguishes it from sibling delete_*_attachment tools, though it never names 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?

The description only says what it does, not when to use it versus the many sibling attachment tools (delete_issue_attachment, delete_test_result_attachment). No prerequisites, no conditions, no exclusions are given.

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