Bitcoin Barometer snapshot

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered structurally. The description adds one useful behavioral note — 'Descriptive only,' implying no advice or interpretation is returned — but says nothing beyond that about freshness, caching, or limits.

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 sentences, front-loaded with what the snapshot is before listing contents. The content enumeration overlaps with the output schema, but the brevity keeps it from being wasteful.

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?

A parameterless read-only tool with full annotation coverage and an output schema needs little description; this one tells the agent what domain data it returns and that it is descriptive only. The only real gap is that it does not help route between the three sibling tools.

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. Baseline 4 applies; no parameter-level confusion is possible.

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 Bitcoin Barometer reading) and enumerates exactly what the snapshot contains — Heat Score, zone/bands, comparative periods, BTC price changes, and the ten indicators. It is clear what the tool returns, but it never distinguishes itself from siblings like get_history or explain_indicator, which an agent could plausibly confuse given the mention of 'yesterday and last week'.

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?

'Descriptive only' hints at the tool's role as a data-only read, but the description gives no explicit when-to-use guidance and never names an alternative. An agent choosing between this, get_history, and explain_indicator gets no routing signal.

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