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 covered. The description adds behavioral value by disclosing the response content (measurement, current value, heat, score contribution), which matters because there is no output schema.

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 tool's function in the first clause, then the valid names. The name list is long but carries real information absent from the schema; no wasted sentences.

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 steps in to say what comes back (value, heat, score contribution), and the enumerated names cover the main failure mode of an invalid parameter. Minor gap: no note on error behavior for an unrecognized name.

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 coverage is nominally 100%, but the only schema text is the bare 'Indicator name' and there is no enum constraint. The description compensates meaningfully by enumerating the ten valid names (monthlyRSI, mvrvZScore, fearAndGreed, etc.), which the schema does not provide.

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 verb (explain) and resource (one Barometer indicator) plus the three things it returns: what it measures, current value/heat, and score contribution. This is clearly distinct from siblings get_history and get_market_snapshot, which concern history and snapshots rather than single-indicator explanation.

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 only implied by the phrasing 'what one indicator measures' – an agent can infer this is the lookup-by-name tool, but there is no explicit statement of when to use this versus get_history or get_market_snapshot, and no exclusions or prerequisites.

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