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

With no annotations, the description carries the full burden and does so well: it discloses the auth mechanism (X-API-Key header or api_key param), tier-gated history windows (free 24h, Pro 31-day, Bot full), and the 5000-row limit. It does not state rate limits or error behavior, keeping it below 5.

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?

Dense and front-loaded: the dataset list and the CSV/backtest purpose lead, with auth and tier constraints after. Every clause carries information, though the run-on pipe-delimited dataset list is slightly awkward.

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?

No output schema, but the description states the CSV return format, and it covers auth plus all tier/limit boundaries an agent needs. The only real gap is the undocumented symbol and exchange parameters.

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% across 7 params, so the description must compensate. It explains dataset, start/end (ISO, UTC), limit (max 5000), and api_key, but leaves symbol and exchange completely undocumented in both schema and description.

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+resource and output form ('Historical rows as CSV, for backtests') and enumerates the exact datasets served, which lets an agent pick it apart from siblings like get_funding_history or get_liquidations. It does not name a sibling to contrast against, 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?

Gives a clear primary use case (backtests), a within-tool alternative for bulk ('for bulk use download_url'), and an explicit row cap at which local retrieval stops being appropriate. It lacks an explicit when-not-to-use framing against the many get_*/history siblings.

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