Bulk Delete Project Webhooks Triggers

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

Annotations already provide destructiveHint: true, so the description's emphasis on 'cannot be undone' is redundant. It adds no new behavioral traits beyond confirming irreversibility and listing required parameters.

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 slightly repetitive ('This cannot be undone' appears twice) and includes endpoint information that may be useful but adds length. It 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?

For a delete tool with destructive annotations and no output schema, the description covers the action and required parameters. However, it omits details about response, error conditions, or scope of deletion, making it minimally adequate.

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?

The input schema covers all three parameters with full descriptions (100% coverage). The description only lists the required parameters without adding detail beyond what is 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 action (deletes multiple triggers) and the resource (project webhooks triggers) in a single request. It distinguishes from other tools by being a 'bulk' delete and specifies the endpoint.

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 describes when to use (to permanently delete webhooks) but does not mention alternatives or exclusions, such as when to use individual delete vs bulk. The context is clear but lacks guidance on choosing this tool over siblings.

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