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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world scope, so safety is fully covered by structured data. The description adds only the word 'recent', giving no ordering, pagination, or truncation behavior, and it does not mention that history depth is plan-gated (that constraint lives only in the schema).

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?

A single front-loaded sentence with no filler, which is structurally sound. It is arguably too terse for the amount of unexplained domain vocabulary, but nothing is wasted.

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?

There is no output schema, so the description carries the burden of describing what is returned, yet it never says what an 'evidence receipt' contains, how results are ordered, or how the limit interacts with a monitor's history. For a tool whose entire value is the returned list, this leaves a significant gap.

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 monitor_id, limit (with its default of 20 and plan restriction), and api_key are all documented in the schema. The description adds no extra meaning about these parameters, 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?

States a specific verb ('List') and resource ('evidence receipts for a monitor'), so an agent knows it retrieves recorded history for a given monitor. However, the name says 'changes' while the description says 'receipts', and neither the term 'evidence receipt' nor its relationship to a 'change' is explained. No sibling tool does the same thing, so differentiation is not a practical problem.

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 when-to-use guidance, no conditions, and no mention of the alternatives an agent might reach for (e.g., fluxproof_check_now to produce a fresh check versus this tool to read past ones). The agent must infer that this is the read-history counterpart 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.