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

With no annotations, the description carries the full burden and does disclose a real behavioral trait: a metered cost of $0.002 USDC per call, which matters for agent budgeting and retry loops. It still omits auth requirements and whether the price/fill data is real-time or cached, so it falls short of a 5.

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?

Three tight sentences: purpose first, returned fields second, symbol format third, cost last. No hedging or filler, and the most decision-relevant information is front-loaded.

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?

With no output schema and no annotations, the description compensates well by listing the returned metrics (oracle price, mark price, 24h change, open interest, fees, funding rate, fills) and the cost. Missing only edge-case behavior for invalid or ambiguous symbols.

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 coverage is 100% for the single 'symbol' parameter, and the schema already supplies both suffixed and unsuffixed examples. The description's symbol guidance largely duplicates that, though it does reinforce that the '-BET' suffix is optional. Baseline 3 applies when the schema does the work.

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 and resource ('Get detailed info for a specific Drift BET prediction market') and enumerates the fields returned, so the agent knows exactly what data class it gets. It does not explicitly distinguish itself from close siblings like drift_prediction_markets or drift_market_history, which is the only thing keeping it from 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?

Usage is only implied: the symbol examples suggest a per-market lookup versus a listing tool, but the description never says when to pick this over drift_prediction_markets or drift_market_history, nor what happens for an unknown symbol. Adequate but leaves the routing decision to inference.

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