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

Annotations declare it is not read-only, not destructive, and not open-world, so the safety profile is partially covered. The description adds nothing beyond the endpoint string: no permission requirements, no reversibility/revocation note, no error behavior for invalid user ids.

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?

Very short and front-loaded, with the action stated first. The appended raw endpoint ('POST /api/v2/webhook/bot/share/{id}') is somewhat redundant with the name but harmless and mildly informative about routing.

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 tool with no output schema, sparse annotations, and undocumented parameters, the description is far too thin. It omits prerequisites, payload expectation, and success/failure semantics, so an agent cannot call it confidently.

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 effectively 0% for the top-level parameters; only the nested userId carries a description. The description adds no meaning to the '{id}' path parameter or the body shape beyond reusing the word 'user', 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 clear verb+resource: 'Share webhook with user', backed by the endpoint path. An agent can understand the action. However, it does not differentiate from the near-identical sibling post_webhook_data_share_id, which shares a different webhook resource, leaving the object of the share ambiguous.

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?

No when-to-use context, no prerequisites (e.g., the target user must exist / be a friend), and no mention of alternatives such as post_webhook_data_share_id or the get_..._shares readers. The agent is left to infer everything about selection.

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