get_clob_simplified_markets

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

No annotations are provided, so the description must carry behavioral context. It discloses the performance tradeoff (faster, less detail) and pagination via cursor, which adds value. But it doesn't mention rate limits, authentication requirements, expected response size, or pagination termination behavior.

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?

Front-loaded with purpose and scope, followed by the comparison to the sibling and a targeted Args section. Every sentence adds information without redundancy.

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 an output schema exists, the description needn't explain return values. It covers the tool's purpose, the performance tradeoff, and the sole parameter's semantics. It could be more complete by mentioning authentication or rate limits, but for a read-only overview tool it's nearly sufficient.

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 description coverage is 0%, so the description must compensate. It explains the next_cursor parameter: it's a pagination cursor from a previous request, and omitting it fetches the first page. This adds meaningful semantics beyond the empty schema. A 4 rather than 5 because it doesn't describe cursor format or maximum page size.

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), resource (paginated simplified list of prediction markets), scope (actively trading on the Polymarket CLOB API), and explicitly distinguishes it from the sibling get_clob_markets by stating it provides less detail but is faster.

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?

Clearly states when to use this tool (overview data, faster) and names the alternative (get_clob_markets) with the tradeoff. However, it doesn't give explicit when-not conditions or describe scenarios where the fuller detail is required.

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