Delete Equipment Attachment (Project)

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

The description explicitly states 'This cannot be undone' and 'permanently removes', aligning with annotations (destructiveHint=true). It also provides API version and endpoint, adding clarity beyond annotations.

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 repetitive, stating 'permanently delete' and 'cannot be undone' twice. Could be more concise while retaining essential information.

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?

While the description includes the endpoint and required parameters, it lacks information about return values (no output schema), required permissions, or side effects on related data, which would be helpful for a deletion tool.

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?

All 4 parameters are described in the input schema with 100% coverage. The description merely repeats the required parameter names without adding new semantic context beyond the schema.

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 equipment attachment (Project)' and explains it permanently deletes Equipment records. The title and context differentiate it from similar sibling tools like delete_equipment_attachment_company.

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 says to use it for permanent deletion and notes irreversibility, but provides no guidance on when to use this tool vs. alternatives, nor prerequisites or conditions for safe use.

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