mailkite_list_delivery_attempts

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

The description discloses behavior not visible in annotations or schema: newest-first ordering, what is captured (request payload and response status/headers/body), the 45-day retention limit, and the management session token requirement. This is rich operational transparency.

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?

The description is compact and well-ordered: what is returned, ordering, purpose/alternative, retention, auth. Every sentence carries useful signal without redundancy.

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 single-parameter read-only endpoint, the description covers the input concept, output contents, ordering, retention, and authentication; an agent has enough to decide and invoke it 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?

The schema already documents the sole parameter as a required string 'id' with 100% coverage衣柜? Need not. The description adds that the id selects one delivery, but provides no additional parameter constraints or format. Baseline 3 is appropriate.

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 uses a specific verb and resource ('Every captured attempt for one delivery'), states the ordering ('newest first'), and enumerates exactly what is returned (request headers/payload, response status/headers/body). It also distinguishes this from fetching the whole message, making its scope clear against sibling tools.

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?

It explicitly positions the tool as the per-attempt record behind a webhook post-mortem and notes it avoids pulling the entire message. That gives an agent clear situational guidance for when to call this tool versus a message-fetching or retry sibling.

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