Bulk live prices

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's disclosure of optional baselines and full-set retrieval adds marginal value. No contradictions, but no additional behavioral traits (e.g., pagination, rate limits) are mentioned.

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, no wasted words. The first sentence states the core function, the second clarifies a key usage pattern. Front-loaded and efficient.

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 the presence of an output schema and the tool's simplicity (read-only, bulk prices), the description covers essential usage. Some users might benefit from knowing default 'top' limit or field filtering details, but those are in the schema and not strictly required here.

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 the description adds minimal extra meaning beyond the schema. The phrase 'Omit symbols for the full tracked set' essentially repeats the schema description for the 'symbols' parameter.

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 clearly states 'Bulk live prices' with optional baseline overlays, identifying the tool's purpose as fetching current price data. It does not explicitly contrast with siblings like 'get_coin_historical' or 'get_global_market', but the description is specific enough to distinguish its bulk and live nature.

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?

The description implies usage by noting optional baselines and that omitting symbols returns the full tracked set, but it does not provide explicit when-to-use vs. alternatives or when-not-to-use. The agent must infer usage from context.

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