clob_get_prices

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

No annotations provided, so the description carries full burden. It mentions 'quick multi-token quote snapshot' implying idempotent read, and clarifies input as 'CLOB token IDs'. However, it does not explicitly state behavioral traits like idempotency, freshness, or response structure. Still adequate for a simple read tool.

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 concise (under 100 words) and front-loaded with the primary action. Each sentence serves a purpose: action, usage context, preference advice, exclusion, input format, and next step. No wasted words.

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 the tool's simplicity (1 parameter, output schema present), the description covers all necessary aspects: purpose, usage context, input specification, and common follow-ups. No gaps identified.

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 coverage is 100% (1 parameter, args with token_ids array). The description adds meaning by specifying 'list of CLOB token IDs', which goes beyond the schema's description of 'Multi-token lookup arguments.' It clarifies the type of identifiers expected.

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 'Fetch current price quotes for multiple tokens.' It uses a specific verb ('Fetch') and resource ('current price quotes for multiple tokens'), distinguishing it from siblings like clob_get_price (single token) and clob_get_books (full order books).

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?

Explicitly provides when-to-use: 'Use this tool when the user wants a quick multi-token quote snapshot without needing full order books.' Also advises preferring it over repeated single-token calls and explicitly excludes discovery or wallet-level analysis. Suggests a next step (rank tokens or follow up with get_book).

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