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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds nothing beyond that – no mention of permissions required, whether the share is idempotent, whether the target is notified, or what happens if the user is already a collaborator.

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. It is not bloated, but the raw 'POST /api/v2/webhook/data/share/{id}' endpoint echo adds little value to an agent choosing a tool.

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 mutation that grants another user access, the definition omits the behavioral consequences of sharing, has no output schema to describe the result, and leaves the id parameter unexplained. Annotations cover safety but not the share semantics.

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% at the top level; only the nested userId field is documented in the schema. The description does not explain that id identifies the webhook record being shared or clarify the body.userId semantics, so it fails to compensate for the coverage gap.

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 (share) and resource (webhook data) with the target (user), which is enough to distinguish it from siblings like post_webhook_bot_share_id. It doesn't explicitly name the alternative, but the resource noun 'webhook data' carries the 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 guidance on when to use this versus the bot-webhook share variant or the corresponding delete/get share tools. The agent must infer the intent entirely from the name.

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