Get Webhook Subscription

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: no behavior on an unknown ID, no indication of whether the lookup is tenant-scoped or what fields come back.

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 sentences with no padding and the key information front-loaded. The only waste is that the first sentence is an exact duplicate of the tool title, which already appears as structured metadata.

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?

The tool is simple — one ID parameter, rich annotations, no output schema — so not much is required. Still, with no output schema the description could have said what a returned subscription contains, and it omits not-found behavior entirely, leaving it only minimally viable.

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?

There is a single required parameter with 100% schema description coverage ('The unique identifier for the subscription'). The phrase 'by ID' in the description matches but does not enrich the schema, so the baseline 3 applies.

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 says it returns a webhook subscription by ID, which is a retrieval verb plus resource, but the first sentence merely restates the tool title verbatim. It never distinguishes this from list_webhook_subscriptions or explains what identifying the subscription yields, so an agent gets only a minimal sense of purpose.

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 at all. The obvious alternatives — list_webhook_subscriptions for enumeration versus this tool for fetching one record — are never mentioned, nor is any prerequisite such as needing a known subscription ID.

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