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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context about the ledger's contents but does not disclose additional behavioral details such as staleness, error behavior, or whether the ledger is authoritative. This matches the calibration baseline for annotation-covered read tools.

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, well-front-loaded sentence with no filler. The verb and resource appear first, followed by the meaningful content categories that tell the agent what kind of data the ledger holds.

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 parameterless, read-only tool with strong annotations and no output schema, the description is fully sufficient. It names the resource, the content, and the read semantics; nothing needed for correct invocation 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 tool has zero parameters, so the input schema carries no burden and the description needs no parameter-level detail. The description accurately reflects a parameterless read operation, earning the baseline 4 for zero-parameter tools.

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?

Description states a specific verb ('Read') and a specific resource ('first-party interoperability evidence ledger') with concrete content categories (observed facts, inference state, remediation, verification). This clearly distinguishes it from sibling tools like get_observed_event_timeline or get_research_findings.

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 implies the tool is for reading the interoperability evidence ledger, but it does not explicitly state when to use it versus alternatives or exclude cases. The context is clear enough to infer basic usage, but no direct routing guidance is provided.

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