Отключить webhook

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

The description adds minimal behavioral context beyond the tool's basic function. It does not disclose side effects (e.g., permanent removal of subscription), authentication requirements, or the fact that future webhooks will stop. Annotations provide destructiveHint=false, which may mislead, but the description does not contradict 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?

The description is a single sentence, making it concise but overly brief. It lacks important context such as the effect of the action or usage notes, which could be included without sacrificing brevity.

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 simplicity (3 parameters, no output schema), the description is incomplete. It does not explain the consequences of unsubscription (e.g., no more webhooks sent) or mention that a valid, active subscription must exist for the URL.

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%, and each parameter has a description in the schema. The tool description does not add any extra meaning beyond what the schema already provides, so baseline of 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 clearly states that the tool disables a webhook subscription by URL. The verb 'Отключает' (disables) and resource 'webhook-подписку' (webhook subscription) are specific, and the description distinguishes this from sibling tools like messenger_get_subscriptions (read) and messenger_post_webhook_v3 (create/update).

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 provides no guidance on when to use this tool versus alternatives (e.g., messenger_post_webhook_v3 for creating subscriptions). It does not mention prerequisites (e.g., needing an existing subscription) or 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.