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. The description adds nothing beyond that — no mention of the 25-token cap being a batch constraint, no auth note, no rate-limit or data-freshness context, and it restates the name rather than adding behavioral detail.

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?

It is short, but shortness here is under-specification rather than conciseness — a five-word fragment that conveys no actionable information beyond the tool name. Being front-loaded is meaningless when there is nothing to load.

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?

With an output schema present, return values needn't be explained, but the description still fails to clarify the core concept of a 'spread', the batch nature of the call, or its relationship to the singular sibling. For a financial-market endpoint in a crowded toolkit, this is inadequate.

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 100% and the single token_ids parameter is documented there (including the maximum-25 constraint), so the baseline of 3 applies. The description contributes no additional parameter meaning, such as whether omitted ids default to a broader set.

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 'Polymarket token spreads.' is essentially a restatement of the tool name with no verb and no scope. It does not distinguish this batch tool from the sibling polymarket_token_spread (singular) or from polymarket_tokens_prices/midpoints/orderbooks.

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 guidance at all. Nothing tells the agent when to pick the plural 'spreads' tool over the singular polymarket_token_spread or the other polymarket_tokens_* batch endpoints. Absence of any context or exclusion is misleading by omission given the dense sibling namespace.

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