Disable webhook

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

Annotations already indicate destructiveHint=true. The description adds that this 'changes account settings' and that 'Avito will stop sending events', clarifying the consequence. It also warns that resubscription is required, which is useful behavioral context beyond annotations.

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?

Three sentences cover action, effect, consequence, and parameter guidance. No redundancy. Every sentence adds value. Front-loaded with the primary action.

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 description explains the outcome (unsubscribe, stop events, resubscribe needed). With no output schema, the return value is not described, but for a destructive action this is acceptable. Parameter details are delegated to schema. Sibling context and prerequisites (messenger_get_subscriptions) are referenced.

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% with detailed descriptions for all three parameters. The tool description emphasizes the exact URL requirement but does not add significant new meaning beyond the schema's 'must match the one previously subscribed'. Baseline 3 is appropriate.

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 uses the specific verb 'UNSUBSCRIBES' and identifies the resource as 'URL from messenger webhook notifications'. It clearly distinguishes from siblings like messenger_post_webhook_v3 by noting that to resume notifications you must use that tool. The title 'Disable webhook' aligns with the action.

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 tells when to use the tool (to stop notifications) and provides guidance to specify exactly the URL that was subscribed. It references the sibling messenger_get_subscriptions for discovery and mentions the alternative for resubscribing. However, it does not explicitly state when not to use it.

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