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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is clear. The description adds that the data is public and caps the batch at 20, but it does not explain behavior on invalid IDs, unavailable markets, or the shape/order of returned values; the output schema covers returns, so this is acceptable but not rich.

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?

One direct sentence that front-loads the action and object; the 20-ID limit is folded in naturally. No filler, repetition, or digression.

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 a full output schema and comprehensive annotations, this description is nearly sufficient. It could be more complete by naming the closest alternatives or stating what happens if too many IDs are supplied, but those gaps are minor given the structural metadata.

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 schema already specifies 'conditionIds' as an array of 0x…64 hex strings with min/max 20, so the description's 'market condition IDs' adds only the 'market' qualifier and the batch cap. With 0% schema-description coverage, some weight falls on the description, but it does not explain what a condition ID is or how to obtain one.

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 clear verb ('Get'), resource ('open-interest values'), and a concrete boundary ('up to 20 market condition IDs'), so an agent can understand what the tool returns. It does not, however, distinguish this tool from the sibling 'get_open_interest', which appears to cover the same resource, so it stops short of a 5.

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?

No sentence explains when to choose this tool over alternatives such as 'get_market_quotes', 'get_open_interest', or market-specific reads. The only implied signal is that the caller wants open interest for condition IDs, which is not enough guidance for selecting among the many sibling tools.

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