Get Webhook Subscription

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine value beyond them by stating the required OAuth scope (webhooks:read), but discloses nothing about return shape, error behavior, or what the operation yields.

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?

Three short, front-loaded sentences with no padding or repetition. It is terse, though the second and third sentences ('Reads Calendly data') contribute little, keeping it just under a fully earned 5.

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 simple single-resource read with annotations covering the safety profile and no output schema, the definition is minimally adequate. It omits any description of the required webhook_uuid parameter and the returned object, leaving meaningful gaps.

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 coverage is only 50%: 'account' is documented in the schema, but the required 'webhook_uuid' has no description there and the tool description supplies none either. An agent gets no help on what a webhook UUID is or where to obtain one, which is the key required input.

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?

The description names a specific verb+resource ('Get Webhook Subscription'), which is clear enough to distinguish from delete_webhook, create_webhook, and list_webhooks. However, it does not explicitly name or contrast with any sibling, so the agent must infer the differentiation from the tool name alone.

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 statement of when to use this tool versus alternatives such as list_webhooks or get_sample_webhook_data. The only guidance-like content is the required scope, which is a prerequisite rather than a usage condition.

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