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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered elsewhere. The description adds that the data is public (no auth) and that exactly one row is returned, which is useful but thin; it discloses nothing about rate limits or failure modes when the condition id is unknown.

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 efficient, front-loaded sentence with no filler. It is appropriately sized, though it stops short of the extra routing detail an agent in this crowded sibling cluster would benefit from.

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 values need no explanation, and the single parameter is covered. For a read-only lookup this is minimally adequate, but the description leaves ambiguous how this CLOB market tool relates to the other polymarket market endpoints.

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% and the single parameter is fully documented in the schema, so the baseline is 3. The description only restates that condition_id is the lookup key and adds no format or sourcing detail beyond the schema.

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 and resource ('Returns one public CLOB market detail row') plus the lookup key ('by condition id'), which is more precise than the bare name. However, it does not distinguish itself from siblings like polymarket_market_detail or polymarket_market_liquidity, so an agent cannot tell which market tool to pick without reading schemas.

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 when-to-use or when-not-to-use guidance. With several closely named market siblings (polymarket_market_detail, polymarket_market_liquidity, polymarket_market_tags), the description never says when this CLOB endpoint is the right choice over those alternatives.

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