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

The description implies a read-only operation ('list') but does not explicitly state side effects, safety, or whether it modifies state. With no annotations to clarify, the burden falls on the description, which is minimal.

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 a single, focused sentence that front-loads the action and object. It is appropriately sized with no superfluous 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?

Given the simplicity of the operation and the absence of an output schema, the description is adequate for a basic list tool. It does not mention pagination or limit behavior, but these are relatively minor gaps for such a straightforward action.

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 input schema provides parameter names (api_key, monitor_id, limit) and types, but no descriptions. The tool description does not add any meaning beyond the schema, so it relies on self-explanatory names. The coverage is 100%, setting a baseline of 3.

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 clearly states the action (list) and the resource (recent evidence receipts) with a target (a monitor). While it does not explicitly distinguish from sibling tools, the actions of siblings (check, create, offer, preflight) are sufficiently different to avoid confusion.

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 is provided on when to use this tool versus the alternatives. The description only states what it does, without any contextual triggers or conditions for selection.

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