Delete An Equipment

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

Annotations already include destructiveHint:true, so the destructive nature is clear. The description adds emphasis on permanence but does not disclose additional behavioral traits such as required permissions or error handling. No contradiction with 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 verbose and redundant, repeating 'This cannot be undone' and 'Permanently removes the specified Field Productivity records' multiple times. It could be 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?

For a simple delete tool with annotations, the description provides adequate context about permanence and the resource being deleted. However, it lacks information on success response or error conditions. No output schema is provided.

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 100% of parameters with descriptions. The description merely restates that project_id and id are required, without adding new meaning beyond the schema. Baseline score 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?

Clearly states it deletes an equipment associated with a project and removes Field Productivity records. Verb is 'delete' and resource is 'equipment'. However, it does not explicitly differentiate from sibling delete tools like 'delete_equipment' or 'bulk_delete_managed_equipment'.

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 indicates to use it for permanent deletion and notes the action cannot be undone, but provides no guidance on when to use this tool versus alternatives like bulk delete or other delete endpoints. No exclusion criteria are mentioned.

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