polymarket_tokens_spreads

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

Mentions it uses public CLOB market-data JSON, credential-free, and handles up to 25 token ids. However, without annotations, more details about rate limits, response format, or error behavior would be beneficial.

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?

Two sentences: first states purpose, second clarifies authentication requirement. No fluff, all information is relevant and front-loaded.

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 no annotations and no output schema, the description adequately covers what the tool does, what it expects, and returns. Could include how to structure the body (e.g., array of strings), but overall sufficient for a simple tool.

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 shows one required 'body' object with description 'Token ids request body'. Description adds that it accepts up to 25 token ids, clarifying the parameter's content and constraint. This adds value 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?

Clearly states it gets Polymarket token spreads and returns CLOB spreads. However, does not explicitly differentiate from sibling tool 'polymarket_token_spread' (singular), which might cause confusion about batch vs single usage.

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?

Provides context that it works with public data and does not require authentication, but does not specify when to use this vs the singular version or other alternatives. No exclusion criteria.

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