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

With no annotations, the description carries the full burden and does well: it discloses a configuration prerequisite (DRIFT_GATEWAY_URL), a per-call cost ($0.002 USDC), and the exact returned fields including the long=YES/short=NO direction convention. It stops short of stating failure behavior when the gateway is unset or unreachable, which would complete the behavioral picture.

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?

Four short sentences, front-loaded with purpose, then returns, then prerequisites, then cost. Every sentence carries distinct, non-redundant information with no filler.

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?

No output schema exists, and the description compensates by enumerating the returned fields (entry price, implied probability, unrealized PnL, direction). For a zero-parameter read tool this is nearly complete; only the failure/empty-state behavior is left unstated.

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 tool takes zero parameters, so the baseline is 4. The description correctly adds nothing parameter-related and instead spends its words on return shape and prerequisites.

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?

Specific verb + resource + scope: 'Get open Drift BET prediction market positions,' with 'all active positions' delimiting the set. It is easy to separate from siblings like drift_close_position, drift_place_bet, and drift_market_details without opening any schema.

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 implied by 'open ... positions from your configured Drift Gateway' and the prerequisite that DRIFT_GATEWAY_URL be set, but there is no explicit when-to-use statement and no named alternative (e.g., drift_close_position for acting on a position). An agent must infer the call context.

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