get_market_data

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Get market data', implying read-only, but does not describe return format, data scope, rate limits, or any other behavioral traits. This is a minimal disclosure for a tool that overlaps with several siblings.

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?

The description is highly concise, with the main sentence front-loaded and an Args section that directly documents the sole parameter. Every line serves a purpose with no wasted text.

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?

Despite having an output schema and one parameter, the description is incomplete because 'market data' is ambiguous in the context of sibling tools like get_orderbook and get_candles_snapshot. It does not clarify what data is actually returned, making it difficult for an agent to select this tool over alternatives.

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 has 0% coverage with no description for 'coin'. The description compensates by defining 'coin' as a trading pair with examples 'BTC' and 'ETH', adding essential meaning. However, it stops short of specifying accepted formats or edge cases, so it doesn't earn a 5.

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?

Description clearly states 'Get market data for a specific coin', providing a verb and resource. However, 'market data' is generic and does not differentiate from siblings like get_orderbook or get_candles_snapshot, so it falls short of the 5 threshold for explicit sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention whether this tool provides general price data or specific data types, nor does it exclude use cases covered by sibling tools.

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