Delivery log and dead letters (payloads omitted)

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add one genuinely useful behavioral note — payloads are omitted and dead letters are included — but it says nothing about ordering, pagination, or whether retry metadata accompanies dead entries.

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 and front-loaded, but almost the entire sentence duplicates the title and then appends a raw HTTP path, which adds little for an agent that already knows the tool name. No wasted length, but low information density.

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 output schema, the description carries the burden of describing what a delivery record looks like — yet it only notes that payloads are omitted. For a log-inspection tool where the agent must interpret statuses and decide on retries, this leaves significant gaps.

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%, so both parameters (limit, status) are undocumented beyond their types and the status enum. The description does not explain that limit caps result count (max 500) or that status filters to pending/delivered/dead, leaving the agent to guess default behavior and default limit.

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 text identifies the resource — notification deliveries, including dead letters, with payloads omitted — and the GET path implies a read/list operation. But it is essentially the title repeated verbatim with an endpoint appended, and it never clarifies how it differs from the many other list/listDeliveries siblings (conversions_listDeliveries, reports_listDeliveries) or from notifications_retryDelivery.

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?

No guidance on when to use this tool versus alternatives; nothing says whether this is for auditing failures, monitoring delivery health, or that dead letters should be followed up with notifications_retryDelivery. The agent must infer all routing decisions from the name alone.

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