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

Annotations cover readOnly and idempotent, but the description adds substantive context beyond them: that current hiding/attribution controls apply to retained history, that no target body/contact/payout address is returned, and that it never signs payments. These privacy and safety guarantees are exactly the kind of behavioral detail annotations don't convey.

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?

Four tight sentences with the scope and privacy guarantees front-loaded. Minor oddity in 'never signs payments' for a read-only tool, but overall efficient with little wasted text.

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 five-parameter tool with no output schema and 0% parameter coverage, the description should explain pagination behavior and what a returned observation contains. It gives privacy exclusions but leaves parameters and return shape undocumented, so an agent cannot call it correctly without opening the schema and guessing.

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% across five parameters. The description loosely implies page size/cursor via 'page through' and listing scope via 'one listing,' but never explains limit, since, cursor, route_id, or listing_id semantics or units. With zero coverage it must compensate and does not.

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 (page through) and resource (monitoring observations / health checks) with scope split between one listing or the whole visible catalog. The phrase 'fixed safe monitoring observations' is somewhat idiosyncratic, but the agent can tell this returns paged health/observation records rather than a scan report or status.

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?

Implied usage: it hints that providing a listing scopes to that listing, otherwise the whole visible catalog is returned. However, it never states when to prefer this over siblings like get_scan_report, get_scan_status, or list_conformance_checks, so the selection guidance is only implied.

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