polymarket_get_live_price

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

Annotations already declare readOnlyHint=true, and the description reinforces a safe read operation. It adds behavioral context by listing returned fields and emphasizing freshness over cached data. No contradictions or missing behavioral traits beyond annotations.

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 extremely concise, consisting of two sentences. It front-loads the core purpose in the first sentence and adds critical detail in the second. No redundant or irrelevant 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?

Given there is one parameter and an output schema exists, the description adequately covers what the tool returns and its freshness advantage. It could be slightly more explicit about its relationship to sibling tools, but overall it is complete for an agent to understand when and how to use it.

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?

With 0% schema description coverage, the description fully compensates by explaining that token_id is a CLOB token id (one of a market's clobTokenIds) and explicitly clarifying it is NOT a slug or conditionId. This adds crucial meaning beyond the schema type.

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 returns 'live odds' for one outcome token from the CLOB, specifies the token_id parameter is a CLOB token id (not slug or conditionId), and lists the returned fields (midpoint, best bid/ask, spread, probability_pct). It distinguishes itself from related tools like Gamma's cached prices, making its purpose unambiguous.

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 implies when to use this tool by stating it provides 'fresher than Gamma's cached prices', suggesting it is for real-time needs. However, it does not explicitly mention when not to use it or provide direct alternatives among siblings.

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