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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful framing that the response is explanatory (meaning plus score contribution) rather than raw data, but discloses no auth, rate-limit, or caching behavior beyond that.

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?

A single tight sentence with the resource and the payload front-loaded, and no filler or restatement of the tool name. Every clause earns its place.

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 need not explain return values, and the read-only annotations cover safety, so the main remaining gap is routing guidance against siblings. For a one-parameter lookup tool it is otherwise complete.

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 100% and the single 'name' parameter carries an enum of ten indicator keys with its own description. The description only restates that it takes one indicator, adding no syntax, format, or validity guidance beyond what the schema already provides, so the baseline of 3 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?

The description names a specific resource (one Barometer indicator) and enumerates the three things returned: what it measures, its current value and heat, and how it contributes to the score. That is far more concrete than a tautology, though it never explicitly contrasts itself with get_market_snapshot or get_history.

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?

There is no statement of when to use this tool versus the siblings. The word 'one' implies a single-indicator lookup, but an agent is left to infer whether indicator values should come from here or from get_market_snapshot, and no prerequisites or exclusions are given.

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

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description only needed to add behavior beyond that — and it does: the 'auto picks the finest that fits 400 points' rule, the 180-point default, and the fact that max_points truncates from the oldest end and sets a 'truncated' flag. That truncation disclosure is genuinely useful for interpreting results. It does not cover rate limits or the public-data freshness caveat.

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 resource is front-loaded and every sentence carries information; there is no filler. The parameter clauses are dense and slightly run-on, which costs a point but not comprehension.

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, return values need not be described, and the description still notes that a summary covers the whole range. Between the annotations, full schema coverage, and the auto/truncation rules, an agent has enough to call it correctly; only edge behavior (e.g. what 'truncated' means downstream) is left implicit.

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 100%, so baseline is 3, but the description goes further than the schema on two params: it explains that interval=auto selects the finest resolution fitting 400 points, and that auto uses max_points=180 while an explicit max_points keeps the latest points and sets a truncation flag. That is real added semantics over the terse schema strings.

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 with scope: 'Heat Score history from the public daily history,' so an agent knows it retrieves a time-series rather than a definition (explain_indicator) or a current-state view (get_market_snapshot). The verb is implicit in 'history' rather than stated outright, and it never names a sibling, 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?

Usage is implied by the parameter framing ('from is required', 'to defaults to the last day') rather than stated as when-to-use guidance. There is no explicit condition distinguishing this from explain_indicator or get_market_snapshot, but the retrieval context is clear enough to act on.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral note is 'Descriptive only', which is consistent but largely redundant with those hints; it adds no auth, rate-limit, or freshness/latency context.

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 resource name and contained in one sentence plus a short qualifier. The enumeration of return fields is somewhat redundant given an output schema exists, but it is compact and readable.

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 zero parameters, a full set of annotations, and an output schema that already defines the return shape, the description covers what an agent needs to decide and invoke. Only the lack of sibling differentiation keeps it from being fully complete.

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 document and the baseline is 4. The description correctly implies no inputs are required.

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 ('Current Bitcoin Barometer reading') and enumerates what it contains, so an agent knows it returns a current-state snapshot. It does not explicitly contrast itself with siblings like get_history or explain_indicator, leaving the reader to infer 'snapshot = current' versus 'history = past'.

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: the word 'Current' plus 'Descriptive only' suggests a read-only, present-tense snapshot, which implicitly contrasts with get_history. No alternative tool is named and no condition for choosing this over a sibling is stated.

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