Destroy Action

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

The description claims both 'sends to Recycle Bin' and 'permanently deletes' without clarifying intent. Annotations already indicate destructiveHint=true, but the description adds internal contradiction, reducing 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?

Five sentences with repetition (cannot be undone twice). Includes API endpoint info, which is useful but could be trimmed. Adequate but not 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?

No output schema; description lacks details on response, error scenarios, or prerequisites. Given many sibling tools, it should clarify recovery options (if any) and distinguish from recycle/restore flows.

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%, so baseline 3. The description mentions required parameters project_id and id but adds no extra meaning beyond the schema. The optional incident_id is not explained.

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 states it destroys an action by sending it to the Recycle Bin and permanently deleting incidents. However, the phrasing is confusing (contradicts 'Recycle Bin' vs 'permanently delete'), and it does not distinguish from sibling 'delete_action' which likely exists.

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 soft-delete or other destroy/delete tools. The description says 'Use this to permanently delete' but does not mention alternative deletion methods or exclusions.

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