clob_get_price

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

No annotations provided, so description carries full burden. It implies a read-only operation (fetch), mentions 'lightweight', and suggests a typical next step, but does not detail side effects or error handling.

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?

Four short, relevant sentences front-loaded with purpose, then usage guidelines, then input clarification, then typical 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?

For a simple price-fetch tool with one parameter and an output schema, the description covers purpose, usage, input, and next step. Missing explicit mention of error cases, but complexity is low.

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% with basic description. The description adds that input is a single CLOB token ID, which is slightly more specific than schema, but does not provide novel semantics beyond what schema offers.

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?

Description clearly states it fetches a current price quote for one token, with specific verb and resource. It distinguishes from siblings by calling it a 'lightweight spot quote' compared to full order book tools.

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 says when to use (user wants current quoted price for known token, no need for full book) and gives alternatives: prefer over get_book, prefer get_midpoint or get_spread for specific metrics.

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