polymarket_tokens_spreads

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the call uses public CLOB market-data JSON and requires no user token, wallet signature, cookies, or account authentication. However, it does not mention rate limits, error behavior, or response structure, so transparency is partial.

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 with the core purpose front-loaded, followed by the key invocation detail (batch limit and authentication-free). No filler or redundant restatement of the schema.

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?

For a single-parameter read endpoint, the description covers the essential invocation context: what it returns, the batch limit, and that no authentication is needed. Without an output schema it could have described the response shape in more detail, but stating the return is public CLOB spreads is likely sufficient for an agent to call it correctly.

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%, but the body parameter description is generic: 'Token ids request body'. The description adds real meaning by specifying 'up to 25 Polymarket token ids' and clarifying that the data returned consists of public CLOB spreads, which helps an agent correctly populate the token_ids array.

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 action (get spreads), the resource (Polymarket tokens), and an important constraint (up to 25 token ids). It is specific about returning public CLOB spreads, but it does not explicitly distinguish itself from sibling tools like polymarket_token_spread or polymarket_tokens_orderbooks, leaving that to the tool name.

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 gives clear context: this is a batch endpoint for up to 25 token ids and requires no authentication, which tells an agent when to use it. It does not name alternatives or state when not to use it, but the credential-free public-data framing is enough guidance for basic selection.

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