Delete Webhook

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds 'permanently', reinforcing the irreversibility but no new behavioral insights. It does not contradict annotations; this is a baseline score given annotation coverage.

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 a single sentence of 5 words, extremely concise. Every word is essential: 'Delete', 'Automox webhook subscription', 'permanently' specifies the action and permanence. No filler or 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?

For a simple delete tool, the description combined with annotations (destructive, idempotent) and schema is nearly complete. It states the core purpose. An output schema is present, so return values are covered. Minor improvement could mention scope like organization-level, but it's 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 schema has 3 parameters with 0% description coverage, meaning no parameter details in the schema. The description does not explain any parameter (e.g., what is 'webhook_id', 'org_uuid', 'request_id' for). It fails to compensate for the lack of schema descriptions, thus adding minimal value for parameter understanding.

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: 'Delete an Automox webhook subscription permanently.' The verb 'Delete' and resource 'webhook subscription' are specific, leaving no ambiguity. It distinguishes from siblings like 'get_webhook' or 'update_webhook' by specifying a permanent deletion action.

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 no guidance on when to use this tool versus alternatives. For example, it does not mention that a webhook can be temporarily disabled via 'update_webhook' instead. The tool is isolated without context for appropriate usage compared to other webhook-related tools.

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