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

Beyond the readOnlyHint annotation, the description adds substantial behavioral context: no auth required, returns untrusted citizen-authored data, and the CallToolResult _meta carries a server-owned provenance boundary. It also explicitly confirms the call changes nothing and is repeatable, matching the annotation without contradicting it.

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?

Two dense sentences accomplish everything: the first front-loads the core purpose and outcome, the second adds security/trust and safety semantics. Every clause earns its place, with no repetition of the schema or annotations.

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 zero-parameter, read-only tool with no output schema, the description is remarkably complete. It tells the agent what the call returns, how to interpret trust (untrusted data, provenance boundary in _meta), that no auth is needed, and that it is safely repeatable. Nothing essential is missing.

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 has zero parameters and 100% schema description coverage, so there is nothing for the description to explain. With no parameters, baseline is 4; the description adds no unnecessary param details, which is appropriate.

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 opens with a specific verb ('Read') and a precisely scoped resource: 'shipped docket changes can be joined to public asks and delivery receipts, with the unjoined rows named.' This goes far beyond the tool name and clearly separates it from the many other read-style siblings like history or events by its unique join semantics.

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?

The description provides context about auth ('No auth needed') and side effects ('READ-ONLY'), but it never states when to choose this tool over a sibling or when not to use it. No alternatives are named, and no conditions are given beyond the general read-only framing.

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