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

Beyond the readOnly/destructive annotations, the description adds useful behavioral context: hidden evidence is withheld, historical write responses are snapshots, and no permissions are granted. It does not contradict the annotations and meaningfully improves the agent's understanding of the tool's behavior.

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 sentences, front-loaded with the read purpose and followed by essential caveats. There is little waste, and the important visibility and snapshot constraints are stated compactly.

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 one-parameter read tool, the annotations and description cover safety and visibility well. However, the description leaves gaps around the id parameter's meaning and when to use this tool versus sibling outcome tools.

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 required parameter, id, is not mentioned in the description, and schema description coverage is 0%. The agent can infer it is an outcome ID from the tool name and pattern, but the description adds no semantic meaning about the identifier.

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 read operation over outcome evidence and related concepts such as provisional independence, reversals, and credit. It is clear what the tool does, but it does not explicitly distinguish itself from siblings like review_outcome, appeal_outcome, or submit_outcome.

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 gives no explicit when-to-use guidance, prerequisites, or named alternatives. It implies this is for reading public outcome evidence, but does not tell the agent when to choose it over review_outcome or appeal_outcome.

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