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

With no annotations provided, the description carries the full disclosure burden, and it does so well: idempotency on repeated calls, that the caller's own session bearer is used, and that the webhooks:delete scope is required. It stops short of stating whether a missing uuid errors or succeeds silently and what (if anything) is returned.

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?

Four short sentences, front-loaded with the action, then idempotency, auth, and scope. No filler, no repetition of the schema, and every sentence adds operational value.

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 one-parameter delete with no output schema and no annotations, the description supplies the key missing context: auth mechanism, required scope, and idempotency. Minor gaps remain around error behavior for unknown UUIDs and whether a confirmation payload is returned.

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% and the single parameter is fully documented in the schema, including where the UUID comes from. The description adds only the phrase 'by uuid', so baseline 3 applies – the schema does the heavy lifting.

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?

States a specific verb ('Delete') and resource ('webhook endpoint') plus the identifier used ('by uuid'), which cleanly separates it from create_webhook, update_webhook, get_webhook, and list_webhooks among the siblings. An agent can select it without opening the schema.

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 operation type makes basic usage inferable (you delete an existing webhook you no longer want), but there is no explicit when-to-use guidance, no mention of alternatives such as update_webhook for disabling versus deleting, and no stated precondition like 'the webhook must exist'.

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