Disable webhook

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

Annotations already indicate destructive and non-idempotent. Description adds 'Changes account settings' and 'Avito will stop sending events', explaining the irreversible effect. No contradiction.

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 concise sentences: action+effect, consequence+resume path, URL requirement. Front-loaded with no redundancy.

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?

No output schema, but description covers core usage. Missing response details (e.g., success indicator) but adequate for a simple destructive action. With annotations, sufficiently 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 covers all 3 params (100%). Description emphasizes url must match subscribed one, adding context beyond schema. dryRun and idempotencyKey already well-described in 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?

The description explicitly states 'UNSUBSCRIBES the specified URL from messenger webhook notifications', identifying the action and resource. It distinguishes from siblings by referencing messenger_post_webhook_v3 for subscribing and messenger_get_subscriptions for listing.

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?

Clear guidance: use to unsubscribe, resume via messenger_post_webhook_v3, and specify exactly the subscribed URL (hint to use messenger_get_subscriptions). Implicitly excludes using for other purposes.

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