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

No annotations are provided, so the description carries the full burden. It mentions nothing about caching behavior (only implied by the schema's forceRefresh), rate limits, per-query partial-failure handling, or auth requirements – significant gaps for a batch network call.

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 short, front-loaded sentences with no filler and the batch nature stated first. It is efficiently sized, though extremely terse for a tool with behavioral nuances.

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?

Inputs are fully covered by the schema and no output schema exists, so the description needn't explain return values. But with no annotations, it should say more about result ordering, per-query error semantics, and caching – gaps that matter for a batch tool.

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%, so the schema already documents queries, symbol, provider, chain, and forceRefresh. The description only restates the maxItems=20 cap already encoded in the schema, adding no new parameter meaning.

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 and resource ('Fetch prices') with explicit batch scope ('multiple assets/providers in a single request'). This implicitly separates it from the singular get_oracle_price sibling, but it never names an alternative outright.

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?

'multiple ... in a single request' implies the batch use case, so an agent can infer when this beats the single-asset tool. However, there is no explicit guidance on when to prefer it over get_oracle_price, get_consensus_price, or get_oracle_health, and no exclusion criteria.

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