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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's only added signal is that results carry response status codes; it says nothing about ordering, retention window, or how pagination behaves.

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 a single short clause with no wasted words, but it reads as an under-specified label rather than a front-loaded explanation. Brevity here comes at the cost of content rather than from efficiency.

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 four-parameter listing tool with no output schema, the description should at minimum tell the agent when to pick this over list_webhooks or replay_failed_webhooks. Annotations and schema carry the mechanics, but the selection and return-content story is incomplete.

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 100%, so all four parameters (limit, cursor, event_id, endpoint_id) are already documented, including the useful 'status_callback' special value for endpoint_id. The description adds no parameter meaning beyond that, 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 fragment identifies a specific resource — delivery attempts to webhook endpoints — and adds that response status codes are included. But it is a noun phrase with no verb and no scope statement, and it does nothing to distinguish this from siblings like list_webhooks, get_webhook, or replay_failed_webhooks.

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, no mention of the relationship to replay_failed_webhooks or list_webhooks, and no note about pagination workflow despite a cursor parameter. The agent must infer everything about tool selection.

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