get_clob_market

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about auth requirements, rate limits, caching, or what happens when the condition_id is unknown. "Detailed, comprehensive" is marketing framing rather than behavioral disclosure.

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?

One front-loaded sentence stating purpose and scope, followed by a minimal Args line. No filler beyond the slightly redundant restatement of the parameter in docstring form.

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?

An output schema exists, so return-value detail is not needed. What is missing for a single-resource lookup tool is how to source the condition_id, error behavior for invalid ids, and routing versus the plural/gamma market siblings.

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 0% and the schema only labels the field "Condition Id", so the description's "unique on-chain identifier corresponding to the specific market's conditions" genuinely adds meaning. However, it does not give the expected format (hex, length) or where to obtain the 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?

States a specific verb ("Retrieve") and resource ("a single Polymarket prediction market") with detail scope. The word "single" implicitly contrasts with the list-oriented siblings get_clob_markets/get_clob_simplified_markets, though no sibling is named explicitly.

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?

No guidance on when to choose this over get_clob_markets, get_gamma_market, or search_markets, and no prerequisites (e.g., where a condition_id comes from) are stated. Usage is only implied by the word "single".

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