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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing behavioral — no note on pagination, retention window, or volume of deliveries — and merely forwards the agent to describe_operation.

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?

It is short, but the first two sentences are an identical duplication of the same path string, so half the text is pure waste. The remaining operation-ID line is machine boilerplate rather than front-loaded useful information.

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 list-shaped read with a nested 'query' object, no output schema and zero parameter documentation, the description should say what a delivery record represents and how results are paged. None of that is present, so an agent cannot predict the response or shape the query correctly.

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 description coverage is 0% for two parameters, so the description must compensate and does not. It never explains that 'params.id' is the outgoing webhook identifier or what the free-form 'query' object supports (filters, paging, sorting), leaving both parameters undocumented everywhere.

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 only repeats the raw endpoint path verbatim, which is the same information already in the name and title. It does not explain that the result is a list of delivery attempts/records for a specific outgoing webhook, so an agent learns nothing about the resource beyond HTTP verb and route.

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 versus siblings such as get_webhooks_outgoing_ec27882af290f545aaaabd1e or get_webhooks_outgoing_by_id_secret_dd7a5ad3dfdb5d9eccb38e97. The only routing hint is a pointer to describe_operation for request schemas, which is a schema-retrieval tip rather than usage guidance.

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