Destroy Property Damage

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

The description adds behavioral info beyond annotations by emphasizing irreversibility ('This cannot be undone') and the Recycle Bin mechanism. It repeats this twice, but still adds value. 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 contains repetition ('This cannot be undone' twice, 'Permanently removes' repeated). It also includes technical API details that may not be necessary for an agent. 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?

The description does not mention the optional parameter 'incident_id' or explain when it's needed. It also lacks information about return values or success/failure behavior after deletion. With no output schema, this is a notable gap.

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 description coverage is 100%, so baseline is 3. The description lists required parameters but doesn't add meaning beyond the schema. It mentions 'Required parameters: project_id, id' which is redundant with schema's 'required' field.

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 it sends a Property Damage record to the Recycle Bin for permanent deletion. It uses specific verb 'destroy' and resource 'Property Damage', and distinguishes from other tools like list, show, update, and create property damages.

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?

It explicitly states 'Use this to permanently delete the specified Incidents', providing clear usage context. However, it doesn't mention when not to use or compare with alternative deletion methods, but given the name and context, it's sufficiently clear.

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