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

Annotations already cover safety (readOnlyHint, openWorldHint), and the description adds real behavioral context beyond them: the quote is independent, it includes estimated taker fees and depth, and Kalshi returns degraded identifier-only results. That last point materially changes what an agent should expect from a valid call.

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?

Two tight sentences: the core capability first, then the platform-specific exception. Every clause carries information; the documentation URL is the only mildly expendable element.

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-shape explanation is unnecessary, and the caveat about Kalshi's reduced output is exactly the kind of pre-call expectation an agent needs. Missing only explicit guidance on when to prefer the multi-venue comparison sibling.

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 schema already documents side, platform, market_id, and amount_usd with defaults. The description adds nothing about parameter formats or constraints, 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?

States a specific verb+resource ("Get an independent Polymarket all-in order-book quote") and scopes it to a single venue, which implicitly contrasts with the sibling compare_executable_quotes. It does not name that sibling outright, so an agent must infer the multi-venue alternative.

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 Kalshi caveat ("requests return only identifiers and a notice") implies Polymarket is the useful path for real quotes, and "one venue" implies compare_executable_quotes is the multi-venue option. However, there is no explicit when-to-use/when-not statement or named alternative, leaving routing to inference.

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