delete_webhook

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

No annotations provided, but description discloses idempotent behavior, 404 for missing ids, and impact (stops POSTing events). Lacks discussion of authorization or reversibility beyond delete, but sufficient for most agents.

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?

Well-structured with sections (WHAT IT DOES, WHEN TO USE, RETURNS, RELATED). Every sentence adds value; no wasted words.

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, covers purpose, usage, return format, and idempotency. With no output schema, the RETURNS section is valuable. Missing details on error scenarios beyond 404, but overall 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?

Schema coverage is 100%, so schema already documents parameters. Description adds context for 'id' by referencing list_webhooks/register_webhook and notes 'api_key' can be from env, which adds slight value beyond 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?

Clearly states 'Unsubscribe one of the agent's webhooks by id' and 'deletes the subscription'. Distinguishes from siblings list_webhooks and register_webhook via explicit 'RELATED' section.

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?

Includes 'WHEN TO USE' with specific scenarios like rotating URLs, retiring agents, narrowing scope. Could be improved by adding explicit when-not-to-use, but current guidance is clear and helpful.

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