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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It exceeds that burden: it discloses the retirement status, the price of 0.00, the fact that no payment can settle, and the historical bug where the previous $0.01 price caused a charge-then-refund cycle. This is exemplary transparency about a defective tool.

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?

Front-loaded with 'RETIRED' and efficient overall, but somewhat verbose with the RQ code, exact date, and detailed historical bug narrative. Every sentence does earn its place for a retired tool — the charge-then-refund explanation is important context — though it could be tightened without losing meaning.

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?

Completely adequate for a retired tool: it states retirement, why it's unusable, what happens when called, and points to the decision document for details. No annotations or output schema exist, and the description fully compensates. Nothing an agent needs to avoid misusing this tool is missing.

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% — the single 'task' parameter is documented in the schema. The description adds no parameter-level detail, which is acceptable given full coverage. Baseline 3 is appropriate; the description's value lies in retirement disclosure, not parameter semantics.

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 leads with 'RETIRED' and immediately states what the tool cannot do: there is no market state to query because the underlying contract has zero markets. It names the specific verb-resource relationship (querying market state via prediction.oracle) and clearly differentiates itself from siblings by declaring itself non-functional. An agent can tell immediately this tool should not be selected.

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?

Explicitly states when not to use it: 'NO 402 challenge is issued and no payment can settle.' It explains the failure mode (charge-then-refund cycle) and references the decision document for rationale. This is stronger than typical guidance because it actively prevents misuse rather than merely describing intended use.

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