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 non-obvious context worth having: credentials of a webhook are never exposed in the response, and the underlying endpoint is GET /webhooks. It does not mention pagination or response envelope shape.

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 compact sentences plus the endpoint reference; every clause carries information (fields returned, credential-hiding behavior, method/path). Front-loaded with the verb+resource, no filler or restated title.

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 no-argument read tool with no output schema, the description supplies the key facts an agent needs: what record fields come back, that secrets are withheld, and the HTTP endpoint. Only pagination and result ordering are left unaddressed.

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?

The tool takes zero parameters, and the description correctly implies an account-wide, unfiltered listing rather than suggesting optional filters. Baseline 4 applies for a no-parameter tool.

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 and resource (list webhooks in the account) and enumerates what is returned (target URL, event types, deactivated flag). It is distinguishable from sibling list_* tools by resource, though it doesn't say what a webhook is used for beyond the field list.

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?

Usage is only implied: an agent can infer this is the discovery call for webhook configuration. There are no explicit when-to-use/when-not conditions, no prerequisites, and no sibling routing (none of the listed siblings is a webhook tool, so there is little to route against).

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