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

Annotations already cover read-only, idempotent, and open-world, so the description's job is to add behavioral context — and it does: data is paper/hypothetical, contains no prices, is free, and requires attribution. That is meaningful disclosure an agent cannot get from the annotations. It falls short of stating freshness or update cadence.

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 usage condition and data scope are front-loaded in a single sentence, with licensing/attribution trailing as metadata. The "Free. License: ... Attribution required: ..." run is boilerplate but short and relevant to whether an agent may use the output.

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, the description must carry return-shape information; naming the risk-on fraction and exposure helps, and the "no prices" caveat is useful. However, it says nothing about update cadence, data staleness, or the concrete fields returned, leaving an agent to discover those at call time.

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 the baseline is 4 and there is nothing for the description to disambiguate. No misleading or unnecessary parameter talk is present.

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 specific resource — the cev-os Trend Vol-Target bot's current risk-on fraction and exposure — with a clear read intent. Naming the exact bot and data fields distinguishes it from siblings like get_macro_regime and get_market_mood, though it never explicitly contrasts with them.

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?

"Use this when you want..." gives a positive trigger condition, which is more than nothing. But there is no when-not guidance, no mention of the sibling regime/mood tools an agent might confuse this with, and no note on the paper/hypothetical scope as a selection criterion.

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