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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the tool returns 'real-time, 1-minute interval price data' and mentions trading volume, but does not disclose potential limitations like data availability range, authentication requirements, or response format details.

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 filler. The first sentence states the core function, and the second adds usage context. Every word earns its place.

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?

For a 3-parameter tool with clear schema descriptions and no output schema, the description sufficiently explains the data type (price, volume) and interval. It lacks explicit mention of optional date parameters' default behavior, but overall it is solid.

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 input schema has 100% coverage with clear descriptions for symbol ('Cryptocurrency symbol (e.g., BTCUSD)') and dates ('Start date (YYYY-MM-DD)'). The description does not add further parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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 the verb 'Get' and specifies the resource: real-time, 1-minute interval price data for cryptocurrencies. It distinguishes from sibling tools like getCryptocurrency5MinuteData and getCryptocurrency1HourData by explicitly naming the 1-minute interval.

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 for monitoring short-term price fluctuations and trading volume ('Monitor short-term price fluctuations and trading volume to stay updated on market movements'), but does not explicitly mention alternatives or when not to use this tool compared to other crypto interval tools.

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