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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without the description. The description adds nothing further — no pagination behavior, no indication of what fields each listed webhook contains, no note about result ordering or limits.

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?

A single four-word sentence with no filler and the action front-loaded. It is efficient but borders on under-specification for a tool that sits among several similarly named webhook operations.

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 parameters, no output schema, and rich annotations, the definition is minimally sufficient to call the tool. Yet nothing tells the agent what the returned list looks like or how this relates to the sibling webhook read tools, leaving a real gap for a simple but crowded namespace.

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, so there is nothing for the description to disambiguate against the empty input schema. Baseline 4 applies; only the absence of any hint about whether filtering or paging is possible keeps it off a 5.

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 gives a clear verb+resource ('List webhook endpoints') that an agent can map directly to the tool's effect. It does not, however, distinguish this from nearby siblings such as get_webhook, list_webhook_deliveries, or create_webhook, so the boundary between similar-sounding tools is left to the agent.

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 choose this over get_webhook (single webhook detail) or list_webhook_deliveries (delivery history). The description states what the tool does but supplies no selection criteria or prerequisites.

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