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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered structurally. The description only restates this with "Remove" and adds an HTTP endpoint path; it does not disclose what exactly is destroyed (the share relationship vs. the bot itself), whether the action is reversible, or any permission requirements.

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?

Two short sentences, with the purpose front-loaded ahead of the API path. Nothing is padded, though the raw endpoint string adds little for an agent that already has the tool name.

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?

For a destructive mutation with two parameters (one entirely undocumented), no output schema, and no annotations covering side effects, the description is thin. It omits the effect of the call, error conditions, and what the required body must contain.

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 description coverage is reported at 0%: the required `id` parameter has no description anywhere, and only the nested `body.userId` is documented in the schema. The description compensates for none of this, adding no meaning beyond the literal "{id}" in the endpoint path.

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?

States a specific verb and resource ("Remove webhook share") that matches the destructive operation the tool name implies. It is clear enough to separate from most siblings, though it does not explicitly distinguish a bot share from the sibling delete_webhook_data_share_id, leaving the name to carry that differentiation.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as delete_webhook_bot_id or post_webhook_bot_share_id. The agent must infer the usage context entirely from the name and annotations.

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