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

No annotations are provided, so the description carries the burden. It discloses valuable behavioral context: the data comes from archived trade streams of Binance, Bybit, OKX, Bitget and Gate, and describes the returned structure (30 price levels). However, it says nothing about permissions, rate limits, pagination, or freshness of the archive, leaving gaps for a no-annotation tool.

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 and its payload, followed by usage routing and parameter constraints. It is dense and runs as one paragraph, but essentially every clause earns its place with no 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?

Given no output schema and no annotations, the description does the work of explaining return content (taker buy/sell volume and trade count per price level) and all parameter ranges. It is nearly complete, with only operational details like rate limits or upstream latency left unstated.

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 description coverage is 0%, so the description must compensate, and it does: symbol is constrained to BTCUSDT/ETHUSDT/SOLUSDT only, minutes is the look-back window bounded 15-10080, and step is the candle size in minutes bounded 1-240. This fully documents all three otherwise-bare parameters.

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 (footprint chart data) and details exactly what each candle contains: taker BUY/SELL volume in USD plus trade count at each of 30 price levels. It explicitly distinguishes itself from get_cvd for net flow by trade size, so an agent can route correctly without opening a schema.

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?

Names the intended use ('see at which prices aggressive buyers or sellers were absorbed') and names the alternative tool get_cvd with the condition that selects it ('for the net flow over time by trade size'). Clear when-to-use and sibling routing.

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