Bulk Delete Company Webhooks Triggers

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

Annotations already provide destructiveHint and idempotentHint. The description repeats these by stating 'This cannot be undone' and 'Permanently removes', adding emphasis but not substantial new behavioral insight beyond the 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 somewhat repetitive, stating 'This cannot be undone' twice and including the full API endpoint. While it is structured with important info up front, it could be more concise by removing redundancy.

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 lacks information about the return value (e.g., success message) and any limits on the number of triggers per request. It covers required parameters and destructive nature, but is incomplete for a bulk operation without output schema.

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% with parameter descriptions. The description merely restates 'Required parameters: company_id, hook_id' without adding extra meaning or context, so it does not improve upon 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 it deletes multiple triggers for a company webhook in a single request, with the verb 'deletes' and specific resource 'triggers'. It also distinguishes from sibling tools like bulk_create_company_webhooks_triggers and delete_company_webhooks_trigger by emphasizing bulk and permanence.

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 says 'Use this to permanently delete the specified Webhooks' and lists required parameters, providing clear usage context. However, it does not explicitly mention when NOT to use it or alternatives like singular deletion, leaving the agent to infer from sibling tool names.

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