get_live_prices

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

No annotations are provided, so the description carries full burden. It states the tool returns the current best price and is real-time, but it does not disclose the return format, potential edge cases (e.g., inactive markets, zero liquidity), or rate limits. The read-only nature is implied by 'Get' but not explicit.

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 two sentences plus a separate token-ID source line, front-loaded with the main purpose. No filler or redundant restatement of the name; every sentence adds information.

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 2-parameter tool with no output schema, the description covers the core purpose and token sourcing. It does not explicitly contrast with siblings, but the purpose clarity already differentiates it. The mention of 'current best price' gives a reasonable hint of the return value.

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% for both parameters, but the description adds a third source for token IDs ('token_id in get_clob_market') not included in the schema's description. The 'side' parameter meaning is already fully captured in the schema, so the description only adds marginal value.

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 tool gets real-time CLOB prices for Polymarket outcome tokens and returns the current best buy/sell price. This specific verb+resource phrasing distinguishes it from siblings like get_live_spread (spread), get_price_history (history), and get_live_orderbook (orderbook).

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?

Usage is implied: use this for current real-time prices. The description tells you where to obtain token IDs, but it does not explicitly say when to prefer this over alternatives or mention any exclusions. No direct comparison to similar quotes tools.

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