Remove a webhook endpoint

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

The annotations already declare destructiveHint=true and idempotentHint=true. 'Permanent.' adds the irreversible consequence beyond those hints, but says nothing about auth, scope, or side effects. A 3 acknowledges this single useful nuance.

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?

One word is concise but under-specified rather than efficient; it lacks the structure to front-load purpose or behavior. Similar to the 'Process' calibration, the brevity reflects omission, not economy.

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 destructive delete tool, the description omits purpose, parameter meaning, and alternatives. It does disclose permanence, which annotations do not fully cover, so it is not the absolute minimum, but it remains incomplete.

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 sole required parameter endpointId has 0% schema description coverage. The description says nothing about what the identifier refers to, its format, or where to obtain it. No compensation is provided for the schema gap.

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 is the single adjective 'Permanent.' It does not state a verb or resource; the tool's purpose is only inferable from its name and title. This is missing rather than a tautological restatement.

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?

There is no guidance on when to use delete_webhook, when not to, or which alternatives such as update_webhook or list_webhooks might apply. The description gives no context for selection.

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