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

Annotations already declare readOnly/openWorld/idempotent/non-destructive behavior, so the description's safety burden is low. It adds the 'public' access qualifier and the alias relationship, but provides no extra behavioral detail such as rate limits or response conventions; this is adequate 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?

Two short sentences with no filler; the alias is mentioned first and the core purpose follows immediately. Every word 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 single-parameter, read-only getter with a full output schema and strong annotations, the description covers the essential invocation context. Minor gaps like error behavior or handling of invalid IDs would improve completeness but are not critical here.

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?

With 0% schema description coverage, the description compensates by identifying the sole parameter as 'market condition IDs' and capping it at 20. This maps directly to conditionIds and adds domain meaning that the raw schema lacks, though it does not explain the hex format or provide example values.

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 is explicit: it names the exact verb ('Get'), the resource ('public open-interest values'), and the input scope ('up to 20 market condition IDs'). It also identifies the canonical sibling alias, so an agent can distinguish this from the other get_* tools.

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 intended use is implied by the resource name and 'condition IDs' scope, but the description never states when to choose this tool over alternatives or when not to use it. No exclusions or alternative tool recommendations are provided beyond the alias reference.

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