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

With no annotations provided, the description carries the burden well by disclosing the paid nature of the call ($0.003 USDC per call via x402 on Base) and the data returned, including 24-hour hourly price history. It does not cover error behavior, rate limits, or freshness guarantees, but it provides substantial behavioral context for a read-only data endpoint.

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 tightly written sentences with no wasted language. It front-loads the core purpose and then adds the pricing detail, so every sentence earns its place.

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 two-parameter data retrieval tool with no output schema, the description adequately lists the returned fields and pricing/payment requirements. It could be slightly more complete by clarifying how to obtain the required id or what happens on invalid venue/id, but the essential invocation context is present.

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%, so the input schema already fully documents venue and id. The description mentions Polymarket and Kalshi but adds no parameter semantics beyond what the schema provides, making the baseline score of 3 appropriate.

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 states a specific resource and scope: one Polymarket or Kalshi market in detail, including the exact market data fields returned. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like odds_search or odds_top.

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 phrase 'One ... market in detail' implies usage for retrieving a known market rather than searching or ranking markets, but the description gives no explicit when-to-use guidance or sibling alternatives. It also does not mention that odds_search may be needed to discover the required id.

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