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

With no annotations, the description carries the full burden. 'Read' and 'current state' convey a non-mutating retrieval, and the scope is explicit. However, it omits error behavior, whether an outcome must already exist, and any access or prerequisite details.

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 a single, front-loaded sentence beginning with the operative verb 'Read'. It lists the relevant state dimensions without filler or redundancy.

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 one-parameter read tool, the description names the operation and the state dimensions returned. Still, with no annotations and no output schema, it leaves ambiguity about response shape, not-found behavior, and whether any preconditions apply.

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 must compensate, but it only refers to 'an outcome' without explaining outcome_id format, constraints, or usage. It adds little meaning beyond the schema's property name and type.

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 clearly states a read operation on an outcome's current state and enumerates the exact scope: payment, supplier, artifact, verification, and remediation. This effectively distinguishes it from the action-oriented siblings confirm_outcome, request_outcome, and resume_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?

No guidance is provided on when to use this tool versus the sibling tools. The sibling names imply they perform actions, but the description never states whether get_outcome should be used first, for preconditions, or after modifications.

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