get_multiple_prices

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only describes the basic function and provides no details about response format, potential errors, rate limits, network requirements, or whether the operation is read-only. The description is severely lacking in transparency.

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 a single, focused sentence that directly states the tool's purpose without any unnecessary words or repetition. It is concise and well-structured.

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 that there is no output schema and no annotations, the description should explain return values and any relevant context, but it does not. It also fails to differentiate from numerous similar price-checking tools in the sibling list, leaving the agent with insufficient information to choose and use the tool effectively.

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 covers 100% of the parameters with descriptions, including examples for 'pairs' and a default for 'network'. The tool description adds no additional meaning beyond the schema, so it meets the baseline expected when schema coverage is high.

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 action ('Get prices') and the resource ('multiple pairs'), with the added scope of 'in a single call' which implies batching. However, it does not explicitly distinguish from sibling tools like coingecko_get_prices or market_coingecko_simple_price, so it lacks explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. It only states what it does without indicating use cases, exclusions, or prerequisites. The phrase 'in a single call' hints at batching but does not clarify when this tool is preferred over other price-related tools.

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