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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description adds the useful scoping detail that results are limited to the authenticated API key, but says nothing about pagination, ordering, or empty-result behavior beyond what the output schema conveys.

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 front-loaded sentence with no filler; the scope ('authenticated API key') and the returned content ('event subscriptions and recent delivery stats') both earn their place.

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 zero-parameter read with an output schema and rich annotations, an agent has nearly everything needed: scope is stated and the description hints at the payload contents. The only missing piece is any note on how this relates to the webhook-registration sibling.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no filtering inputs are needed by framing it as a full listing for the key.

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 all registered webhook endpoints') plus the scope ('for the authenticated API key'), which is more precise than the title alone. It does not name or contrast with the sibling offshoreproz_register_webhook, so an agent still has to infer the read-vs-write split from the verb.

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: 'list' naturally suggests a discovery/inspection step prior to registering or debugging deliveries, but the description never says when to call it versus offshoreproz_register_webhook or when not to. With zero required parameters the usage is hard to get wrong, but no explicit routing guidance is given.

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