delete_webhook

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

No annotations provided, so description carries full burden. It discloses that the tool is destructive (deletion), uses a draft+confirm pattern, and the confirm call issues webhookDelete against Linear. Draft expiration is noted. Could mention if reversal is possible, but sufficient.

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?

Description is structured with clear line breaks and bullet-like points, front-loading the core action. Sentences are concise, though the draft expiration note could be integrated. Efficient overall.

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?

Given the tool's complexity (3 parameters, destructive with draft flow, output schema present), the description covers the essential procedure and expiration. Missing explanation for the workspace parameter, and no output schema details. Good but not fully complete.

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 0%, but description explains the roles of 'id' and 'confirm_draft_id' in the two-call flow. However, it does not mention the 'workspace' parameter, leaving its purpose unclear. Partial compensation.

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?

Description clearly states 'Delete a webhook' with verb+resource, and distinguishes from sibling tools like get_webhook, create_webhook, update_webhook, list_webhooks. No ambiguity.

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?

Explicitly describes the two-call draft+confirm flow and draft expiration, guiding the agent on correct usage. Lacks an explicit 'when not to use' statement, but the procedure is clear and no conflicting siblings exist.

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