Delete Equipment Attachment (Company)

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

Annotations show destructiveHint=true, and the description repeats that the action cannot be undone, which is consistent. However, the description misstates what is deleted (equipment vs attachment), which contradicts the schema and tool naming. This reduces trust and clarity.

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 contains redundancy ('This cannot be undone' repeated twice) and unnecessary repetition of 'Permanently removes the specified Equipment records.' It is verbose and could be much more concise.

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?

Despite having no output schema, the description lacks details on success/failure responses, error conditions, or required permissions. The API endpoint info is helpful but not sufficient for a complete understanding of the tool's behavior.

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 100% and description lists all required parameters. It does not add extra semantic meaning beyond the schema, but meets the baseline. No detailed parameter constraints or formats are provided.

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 tool name and initial phrase indicate deleting an attachment, but the description then incorrectly says 'permanently delete the specified Equipment records' and 'Permanently removes the specified Equipment records', which is contradictory and misleading. The purpose is unclear due to this inconsistency.

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 versus alternatives like delete_equipment or delete_equipment_attachment_project. The description does not mention context, prerequisites, or exclusions.

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