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

With readOnlyHint=true and openWorldHint=false already declaring the safety profile, the description adds real value beyond annotations: it flags that continuity is not verified (a data-quality caveat the agent cannot get elsewhere) and clarifies that the figures are paper-strategy simulation, not live capital. It stops short of describing freshness, staleness, or the shape of the payload.

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?

Three tight sentences, front-loaded with the identity and payload of the record, followed by two disambiguating caveats. Every sentence carries distinct information and none repeat the name, annotations, or schema.

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 zero-parameter, no-output-schema read tool, the description covers identity, payload, scope exclusions, and a data-quality caveat, and notes that the prospective stance history is linked in the response. What remains thin is return-value shape (period coverage, units, formatting), which the missing output schema would otherwise have to supply.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly avoids inventing parameter-style guidance for a call that accepts no arguments.

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 resource (Liquid State's legacy paper-strategy simulation record) and enumerates what it returns: returns, drawdown, and equity observation counts. It distinguishes its scope by negation ('does not measure paid stance outcomes or live capital'), though it never names a sibling tool directly, so differentiation is inferential rather than explicit.

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?

Usage context is implied rather than stated: the 'does not measure paid stance outcomes or live capital' clause tells the agent when this tool is the wrong choice, and the reference to a linked prospective stance history points at an alternative source. There is no explicit 'use this when' or named alternative.

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