polymarket_tokens_midpoints

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

With no annotations provided, the description must fully disclose behavior. It states that returns are for up to 25 token ids and requires no authentication. However, it does not disclose behavior when more than 25 ids are provided, rate limits, data freshness, or the exact response format.

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?

The description is two sentences: the first states the core purpose, the second adds important authentication context. Both sentences are valuable and there is no unnecessary information. It is efficient 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 there is no output schema, the description should explain the return structure but does not. It mentions the limit of 25 token ids and authentication-free nature, but lacks details on input structure (how to pass tokens in the body) and output format (e.g., mapping of token ids to midpoints). This leaves gaps for an AI agent.

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?

The only parameter 'body' is described in the schema as 'Token ids request body', which is vague. The description repeats this without adding details about the expected format (e.g., array of strings, how to indicate token ids). Schema coverage is 100% but the description adds no new meaning.

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 'Get Polymarket token midpoints', specifying the verb and resource. It mentions returning public CLOB midpoints for up to 25 token ids. However, it does not distinguish from the sibling tool 'polymarket_token_midpoint' (singular), missing an opportunity to clarify when to use the batch version.

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 explains that the tool uses credential-free public market data and does not require authentication, providing context for when to use it. However, it does not mention when not to use it or suggest alternatives (e.g., the singular version for a single token id).

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