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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: newest-first ordering and shortened webhook target URLs. It doesn't mention pagination limits beyond the schema's default, which keeps it from a 5.

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?

Two sentences, zero waste: the record contents and ordering are front-loaded, and the second sentence gives the diagnostic use cases. Every sentence earns its 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?

With no output schema, the description does the work of enumerating returned fields (time, kind, channel, target, trigger, status, error), which is exactly right. Filter parameter semantics are partially left to the schema, a minor gap for a read-only tool whose annotations already cover safety.

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 coverage is 60%, and the description repeats the kind and status enum values that the schema already defines. It adds no semantics for site, limit, or alert_id (the alert_id is documented in the schema as coming from list_alerts). Baseline 3 is appropriate since the schema carries most of the load.

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+resource ('every alert, test and report message that twelvebit tried to send, newest first') and enumerates the fields returned. This clearly distinguishes it from list_alerts, which manages alert configurations rather than delivery history.

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?

Provides concrete usage contexts: 'did my alert fire?' and 'why did the Slack alert fail?', which steer the agent to this tool for debugging delivery outcomes. It does not explicitly name alternatives or exclusions (e.g. use list_alerts to see configurations), so it falls short of a 5.

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