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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, but the description adds genuinely useful context the annotations do not: that it reads credential-free public CLOB market-data JSON and requires no user token, wallet signature, cookies, or account auth. It omits rate limits or freshness/latency characteristics, keeping it short of a 5.

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?

Purpose and scope are front-loaded, and the auth caveat is compact. The final sentence is largely circular and does not earn its place, which is the only notable waste in an otherwise tight description.

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 annotations carry the read-only safety signal. With scope, batch limit, and credential-free auth all covered, the description is nearly complete; only behavioral edge cases like rate limits or error conditions are unaddressed.

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 schema already documents both `side` (allowed values buy/sell, default both) and `token_ids` (required, max 25). The description only repeats those facts, adding no syntax, format, or identifier-provenance detail beyond the structured fields, so the baseline 3 applies.

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?

Starts with a specific verb+resource combination ('Returns public CLOB buy and sell prices') and defines the batch scope ('up to 25 Polymarket token ids'), which separates it from single-token siblings. The explicit callout of polymarket_token_price makes the singular/batch split discoverable without opening either schema.

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 closing sentence names an alternative tool but restates its purpose tautologically ('to get Polymarket token price') instead of stating the selecting condition, so the real criterion (single token vs batch) must be inferred from 'up to 25'. No explicit when-not-to-use guidance is given.

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