Delete Attachment

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

Annotations already indicate destructiveHint=true. The description adds redundant 'cannot be undone' but also misidentifies the resource as 'Inspections' instead of 'Attachment', introducing inconsistency. While the permanence is noted, the confusion detracts from transparency.

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 redundant, repeating 'This cannot be undone' and 'Permanently removes the specified Inspections'. It also includes extraneous API endpoint details. Could be condensed to one clear sentence.

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?

No output schema exists, but the description does not explain the return behavior (e.g., empty response or confirmation). The confusion between attachment and inspection leaves the agent uncertain about the actual resource affected.

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?

Input schema covers all 3 parameters with descriptions; the description merely reiterates the required parameters without adding new meaning. Schema coverage is 100%, so baseline 3 is appropriate.

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 is contradictory and unclear: first sentence says 'Deletes the specified Attachment' but then repeatedly says 'permanently delete the specified Inspections'. This confusion undermines clarity, and with many sibling delete tools, it fails to distinguish itself.

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 explicit guidance on when to use this tool vs alternatives. It lists required parameters but does not provide context on use cases, restrictions, or complementary tools. The description simply states the action without usage direction.

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