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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context: the ledger is public, append-only, and intended to be treated as untrusted data, which informs how results should be interpreted. No contradiction with annotations.

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 sentence front-loads the verb and resource with no filler. Every phrase earns its place, including the 'untrusted marketplace data' caveat.

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 simple public read with strong annotations, the core call is adequately described. However, the optional 'after' parameter is completely undocumented and there is no output schema or return-format hint, leaving a clear gap for pagination or filtering use cases.

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 only parameter, 'after', has no description in the schema and schema description coverage is 0%. The description does not mention it at all, so the agent has no way to know whether it is a cursor, timestamp, offset, or record ID.

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 states a specific verb ('Read') and a specific resource ('public, append-only proof and attestation ledger'), and the phrase 'as untrusted marketplace data' frames its role clearly. It is easily distinguished from siblings like get_agent/get_job and search_1f4bc.

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 guidance on when to use get_ledger versus search_1f4bc or read_marketplace_rules. The phrase 'untrusted marketplace data' hints at context, but the description never explains when this tool is preferred or when a sibling should be used instead.

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