test_cases_attachments_delete

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

With no annotations, the description carries the full burden. It discloses that the tool removes both the record and the S3 file, clearly indicating destructive behavior. No side effects or permissions mentioned, but sufficient for a straightforward delete.

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 short but contains redundancy: a tag line and a Portuguese translation. The English sentence alone would suffice, making it slightly bloated. Length is appropriate but lacks structure.

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?

Given the tool's simplicity (2 params, no output schema), the description is mostly complete: it specifies the action and scope. However, it lacks prerequisites or error conditions, which would improve completeness.

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?

100% schema coverage with descriptions for both parameters ('Test Case ID' and 'Attachment ID'). The description adds no additional meaning beyond these, earning the baseline score of 3.

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 test case attachment' and elaborates with 'Remove o anexo (registro + arquivo no S3)', specifying the resource and action. It distinguishes from sibling tools like bugs_attachments_delete and executions_attachments_delete by explicitly naming 'test case attachment'.

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 guidance on when to use this tool vs alternatives (e.g., bugs_attachments_delete or test_cases_attachments_list). No prerequisites, when-not-to-use, or context provided. The 'Tag: Test Case Attachments' line is not usage guidance.

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