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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that by qualifying the trust level of the returned records (owner-confirmed, unsigned receipts, not certification), though it says nothing about pagination behavior or result-set size despite exposing a cursor.

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?

It is a single reasonably sized sentence with no filler, but the front-loaded content is a disclaimer about evidentiary status rather than the tool's action. The most operationally important fact — that this returns a paginated list of entities — never appears.

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 one-optional-param read tool with full schema coverage, annotations, and no output schema, the description is adequate on trust semantics but incomplete on the essentials: what a returned record contains, how pagination terminates, and how it relates to get_confirmed_entity.

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 100% and the single 'after' parameter is documented in the schema as the nextAfter cursor, so the baseline applies. The description adds no pagination semantics, ordering guarantees, or cursor lifetime details beyond what the schema already states.

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 identifies the resource ('published owner-confirmed public records with unsigned reproducible content receipts') and clarifies what 'confirmed' does and does not mean, but it never states the operation — listing — and never distinguishes itself from the sibling get_confirmed_entity or list_local_markets. An agent must lean on the title to know this is a collection-returning tool.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no mention of the sibling tools that fetch a single entity or a factsheet. The only guidance is an implicit trust caveat ('not independent certification or proof of AI adoption'), which is a data caveat rather than usage routing.

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