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

No annotations are provided, so the description carries the full burden, and it does much of that work: it discloses the data source (vault asset snapshots), the exact return fields, the sign convention for the edge, and that the result is 'reported either way' so lagging performance is not hidden. It does not discuss auth, rate limits, or read-only status explicitly, though 'get' and the absence of parameters make those largely inferable.

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?

Front-loaded with the punchy 'The honest track record:' hook followed by the comparison, the return contents, and the sign convention. Four sentences is slightly more than needed, and 'positive means the daily line won, negative means it lagged, reported either way' is mildly redundant, but every sentence conveys usable 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?

With no output schema and no annotations, the description must explain the return payload, and it does so thoroughly (cumulative returns, edge with sign semantics, day count, verdict-readiness flag) plus names the underlying data source. The only meaningful omission is its relationship to the sibling comparison tool get_shadow_vs_brain.

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. The baseline for a no-parameter tool applies.

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 precise comparison: the vault's daily Smart Allocation line vs a fixed 33/33/33 split, including what each side of the edge means. An agent knows exactly what question this answers. It stops short of a 5 because it never names or distinguishes itself from the closely related sibling get_shadow_vs_brain, leaving the agent to infer which comparison tool to pick.

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 is implied rather than stated: the mention of 'enough history for a headline verdict' hints that this is a periodic performance-check tool, but there is no explicit when-to-use, prerequisites, or exclusion against alternatives. With get_shadow_vs_brain in the sibling list covering a parallel comparison, the absence of routing guidance is a real gap.

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