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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description adds one genuine behavioral fact beyond that — private evidence is filtered out of the response — but says nothing about permissions, missing-ID failure behavior, or freshness staleness semantics.

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 short sentences, zero filler, with the core action and the returned content front-loaded before the privacy caveat. Nothing could be cut without losing information.

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 single-parameter read tool whose annotations already carry the safety profile, the description covers the return shape (conditions, evidence status, version, freshness) and the privacy filter, which is what an agent needs. The only notable gap is that it omits any pointer to a sibling for listing or searching outcomes.

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?

Schema description coverage is 0%, so the description carries the full burden for the single parameter and simply doesn't mention it. The constrained format ('^[a-z]+_[0-9a-f]{32}$', maxLength 64) only appears in the schema, and the description gives no hint about where an outcome_id comes from or what it looks like.

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 resource (a public outcome) and enumerates the returned facets (conditions, evidence status, version, freshness). It is clear on its own, but it never names the obvious sibling search_outcomes to distinguish a single-item fetch from a search.

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 explicit when-to-use, prerequisite, or alternative guidance. The word 'public' implies a contrast with private outcomes but neither states the exclusion as a selection rule nor points to which sibling handles private or bulk retrieval.

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