Bulk Delete Triggers

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds valuable behavioral details: 'Permanently deletes', 'cannot be undone', 'Max 500 triggers', and the constraint that triggers must be in the same hook. No contradictions 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, repeating 'permanently delete' and 'cannot be undone' multiple times. While it includes useful endpoint details, it could be more concise without losing meaning.

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?

Given the tool's simplicity (1 parameter, no output schema), the description covers purpose, constraints, limit, and irreversibility. It lacks detail on response format and error handling, but annotations compensate partly. Sufficient for an AI agent.

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 has one parameter (hook_id) with full coverage. The description only restates that hook_id is required and adds no additional semantic guidance beyond what the schema provides (e.g., format, retrieval method). Baseline 3.

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 verb 'Delete multiple webhook triggers', identifies the resource, and adds constraints like 'All triggers must be within the same hook' and 'Max 500 triggers'. It includes an endpoint reference, making the purpose very clear and distinguishing from sibling tools.

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 provides usage context ('Use this to permanently delete the specified Webhooks') and prerequisites ('must be within the same hook', 'provide company and/or project scope'). However, it lacks explicit when-not-to-use guidance or alternatives compared to sibling tools like bulk_delete_company_webhooks_triggers.

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