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

With no annotations, the description discloses meaningful behavioral traits: the read is idempotent and unknown or foreign ids answer not_found. It does not discuss auth requirements in detail, but the 'owner' framing and not_found semantics provide useful access-control context.

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?

The description is two sentences with the action front-loaded and no filler. Some domain jargon like 'owner-safe face' and 'standing read's next actions' is dense, but every clause contributes 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?

Given the absence of an output schema, the description compensates by listing the main return components and the error behavior. It is largely complete for a single-parameter read tool, though the exact meaning of 'owner-safe face' and 'standing read's next actions' remains domain-specific.

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 coverage is 0%, so the description must clarify `eventId`. It indirectly indicates the id selects 'one settled outcome' and that unknown/foreign ids yield not_found, but it never explicitly states that `eventId` is the receipt/outcome identifier or what type of event id is expected.

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 names a specific verb, 'Read', and a distinct resource: 'one settled outcome as an idempotent owner receipt.' It also itemizes returned content and the not_found behavior, which clearly differentiates it from sibling read tools like get_meter_receipt or get_finding.

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 a settled outcome receipt by id, but it does not explicitly state when to prefer it over sibling receipt/finding tools or when not to use it. No alternatives or exclusions are named.

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