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 free. The description adds substantive context beyond that: it discloses the exact payload shape (each level plus its distance from the current price), which is valuable since no output schema exists. It stops short of stating refresh cadence, the snapshot timestamp, or units.

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 sentence that front-loads the frame ('Where Bitcoin's price stands against the levels traders watch') and then lists the specifics. The enumerated list is long but each item earns its place by naming a distinct returned level; nothing is filler.

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 parameters, the description carries the burden of explaining returns and does so thoroughly by enumerating all seven level families and noting that distance from price accompanies each. Minor omissions remain: it does not state whether values are a live snapshot or historical series, nor the currency/units.

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 and the schema is empty, so the baseline is 4. There is nothing parameter-related for the description to clarify or omit.

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 ('Bitcoin's price' against 'support levels') and enumerates the exact levels returned (200-day, 200-week, 1-year averages, bull market support band, Pi Cycle Bottom, realized price, power-law lines). This makes the tool distinguishable from a generic metric fetcher, though it never explicitly contrasts itself with siblings like get_asset_metrics or get_price_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 when-to-use guidance, no exclusions, and no reference to any alternative tool. The agent must infer from the data listed that this is a technical-analysis snapshot rather than a generic price or metric lookup.

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