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

With no annotations provided, the description must carry the behavioral burden, and it does partially by disclosing the returned fields and that lookup is by symbol. It says nothing about failure behavior for an unknown symbol, rate limits, or authentication, and there is no output schema to fall back on.

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?

A single front-loaded sentence that leads with the returned data rather than the verb, with the input example placed last. No filler or redundant clauses.

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 simple single-parameter read tool with full schema coverage, the description covers input and the shape of the result (which substitutes for the absent output schema). The remaining gap is the lack of differentiation from overlapping siblings, which an agent might need to choose correctly.

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 100% and the single parameter is well documented with a pattern and example ('btc'). The description's own example list (btc, eth, sol) only restates what the schema already provides, adding no new constraint or format detail.

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 names a specific resource (a crypto asset by symbol) and enumerates exactly what data is returned (price, market cap, volume, 24h/7d change), so the agent knows the payload. It does not, however, distinguish itself from near-siblings like get_price_on or get_market, leaving overlap unresolved.

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 gives no indication of when to prefer this tool over alternatives such as get_price_on, get_market, or get_metrics, all of which plausibly overlap. There are no stated conditions, prerequisites, or exclusions.

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