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

Annotations already declare readOnlyHint=true, non-destructive, non-open-world, so the safety profile is covered structurally. The description adds only the raw HTTP path and nothing about what is returned, whether results are paginated, or what an empty share list means, which is thin even against the lower annotated bar.

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 fragments, front-loaded with the purpose, but the raw endpoint string 'GET /api/v2/webhook/bot/{id}/shares' consumes half the text without adding agent-relevant value beyond what the path already implies.

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 exists, so the description would need to convey return semantics, yet it says nothing about the shape or contents of shares. Combined with an undocumented id parameter and many similarly named sibling endpoints, the definition is too sparse for reliable selection.

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 0% and there is a single parameter 'id' whose type is string with no documentation. The description does not compensate by explaining that 'id' is a webhook bot id (as opposed to a share id or data id), leaving the parameter meaning ambiguous against sibling endpoints.

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 generic verb 'Get' plus the resource 'webhook shares' and the REST path, which hints at the bot-scoped resource. However it never clarifies whether 'shares' means the list of users this bot is shared with, which is essential given siblings like get_webhook_bot_shared, get_webhook_bot_shared_by_id, and get_webhook_bot_shared_with_id. Purpose is identifiable but not distinguished from close siblings.

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 mention of the alternative 'shared' endpoints, and no stated preconditions such as needing the bot id or ownership permissions. The agent is left to infer usage purely from the name.

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