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

Beyond the readOnlyHint annotation, it discloses that no auth is required, that results are untrusted citizen-authored data, and that CallToolResult _meta carries a server-owned provenance boundary. That trust/boundary information is genuinely useful context an agent could not get from annotations or an empty 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?

Three tight sentences with the core join semantics front-loaded. The final 'READ-ONLY: this call changes nothing' clause partially restates readOnlyHint, but 'can be repeated safely' adds the idempotency detail, so the redundancy is minor.

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 carries the burden of describing the return: joined rows plus named unjoined rows, untrusted authorship, and the provenance boundary in _meta. It covers the essentials adequately, though it could say more about the shape or volume of the returned data.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies a whole-dataset read rather than a filtered one.

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 ('Read') and a precise resource: the join between shipped docket changes, public asks, and delivery receipts, including that unjoined rows are named. An agent can distinguish this from generic docket or receipt readers, though it never names the closest siblings (e.g. inclusion_proof, checkpoint_consistency) that also concern provenance.

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?

Usage is implied by the provenance/join framing and the 'No auth needed' note, but there is no explicit when-to-use, when-not-to-use, or alternative named among the many sibling read tools. The agent must infer that this is the audit/join view rather than a raw listing.

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