polymarket_midpoint

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint. The description adds useful behavioral context beyond these: auth requirements, the return shape {mid}, and the cross-tool behavior of also answering kalshi_orderbook requests. No contradiction with annotations is present.

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 very short and front-loaded with the core purpose, followed by labeled return and auth lines. The final sentence 'Also answers this: kalshi_orderbook' is potentially confusing but does not significantly bloat the text.

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 one-parameter read-only tool with strong annotations, the description adequately covers purpose, return shape, and auth. It lacks detail on edge cases such as empty order books or the type/range of the midpoint, but given the simple scope and schema richness, it is sufficient.

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 single parameter token_id is fully described in the schema as 'CLOB token id,' so schema coverage is 100%. The description's reference to 'one outcome token' adds minimal semantic value and does not clarify format, sourcing, or edge cases 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?

The description clearly identifies the tool as returning the midpoint between best bid and best ask for one outcome token, which distinguishes it from siblings like polymarket_price, polymarket_spread, and kalshi_orderbook. However, it lacks an explicit verb and the closing 'Also answers this: kalshi_orderbook' introduces ambiguity about scope.

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?

There is no explicit guidance on when to use this tool versus sibling tools like polymarket_price or polymarket_spread. 'Auth: none needed' addresses prerequisites, and 'Also answers this: kalshi_orderbook' hints at cross-tool routing, but this is only implied context, not clear usage guidance.

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