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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that - no indication of what a 'share' record contains, whether it returns users/teams, or any pagination or permission behavior.

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?

It is short and front-loaded, but the second sentence is a raw endpoint restatement that adds little value beyond the tool name. Not bloated, but not fully earning its sentences.

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?

With no output schema, the description should describe what is returned (share entries, their fields), which it does not. It also omits any signposting to the related 'shared'/'shared_by'/'shared_with' siblings, leaving the tool under-specified.

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 the single 'id' parameter is undocumented. The description merely restates it as '{id}' in the path without explaining that it is the webhook data identifier, so it does not compensate for the schema 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?

"Get webhook shares" gives a verb+resource, and the endpoint string hints at the scope (data/{id}/shares). However, among a large family of sibling tools (get_webhook_data_id, get_webhook_data_shared, get_webhook_data_shared_by_id, get_webhook_data_shared_with_id), the description never distinguishes 'shares' from 'shared', 'shared_by', or 'shared_with', leaving the actual purpose 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?

There is no guidance on when to use this tool versus the many closely-named siblings, nor any noted prerequisites or conditions. The reader must infer usage 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.