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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the content scope of the record, which is useful, but says nothing about staleness/freshness of 'live' data, rate limits, or pagination behavior beyond what annotations and the output schema provide.

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 tight sentences: the content scope is front-loaded and the routing hint follows immediately. The parenthetical list is dense but every item earns its place, and there is no filler.

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?

With an output schema present, the description needn't document return values, and it supplies scope plus routing. The remaining gap is that 'live' is never qualified — no indication of refresh cadence or as-of timing — which matters for a zero-parameter snapshot tool.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies a single unfiltered snapshot rather than a queryable surface.

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 (the live paper-trading record) and enumerates its contents — returns, costs, risk, corrections, provenance, sleeve equity and limits — so an agent knows exactly what this returns. It gestures at a sibling distinction ('for why they exist, read the papers') but does not explicitly separate itself from trial_ledger, chain_head, or get_paper, so it falls short of a 5.

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?

It gives a clear selection rule: use this for current strategy performance, and go to the papers for rationale. That is an explicit when-to-use plus an alternative, though the alternative is referenced obliquely ('the papers') rather than by tool name, and no exclusions relative to trial_ledger or chain_head are stated.

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