delete_webhook

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds behavioral context by stating the effect 'switch back to getUpdates', which is useful. However, it does not explain the drop_pending_updates parameter or other side effects, so it does not fully disclose behavior.

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 concise sentence, front-loaded with the action 'Remove webhook integration', and contains no unnecessary words. Every word contributes to understanding.

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?

The tool has one optional boolean parameter and no output schema. The description explains the core purpose but omits the parameter's behavior and potential edge cases. Given the simplicity, it is adequate 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?

The input schema has one parameter, drop_pending_updates, with no description (0% schema coverage). The description does not mention this parameter, providing no guidance on its meaning or usage. Since coverage is low, the description must compensate, but it fails to do so.

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 'Remove webhook integration' and its consequence 'switch back to getUpdates', using a specific verb and resource. It distinguishes from siblings like set_webhook and get_webhook_info by indicating the removal and fallback to polling.

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 implies the use case: use when you want to stop using a webhook and revert to getUpdates. It provides clear context but does not explicitly mention alternatives or exclusions, earning a 4 rather than a 5.

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