Delete Webhooks Trigger

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds emphasis on 'permanently delete' and 'cannot be undone', but does not contradict 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 relatively concise with 4 sentences, but contains redundancy with 'This cannot be undone' repeated twice. Front-loading of scope is good.

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 operation with annotations covering destructiveness, the description adequately covers permanence and scope. No output schema needed. Could mention idempotency but not required.

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 is 3. The description lists required parameters but adds little beyond the schema; the 'and/or' phrasing is slightly ambiguous given that both company_id and project_id are required in 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 the tool deletes webhook triggers permanently, specifies the required parameters, and distinguishes it from sibling tools like bulk_delete_webhooks_triggers by focusing on a single trigger.

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 mentions that triggers must be deleted within a company/project scope but does not explicitly guide when to use this tool versus alternative deletion methods (e.g., bulk delete) or provide exclusions.

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