drift_getPositions

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

Description explicitly states it retrieves data (positions and account info), which implies a read-only, non-destructive operation. Given no annotations, this is a clear behavioral indication. However, no details on potential side effects or limits.

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?

Single, direct sentence with no extraneous information. Highly concise.

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?

Adequate for a simple read tool with 2 parameters and no output schema. But lacks explanation of subAccountId, and doesn't mention response format, pagination, or real-time guarantees.

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 50% (only wallet param has description). The tool description adds no parameter-specific meaning beyond the schema, and the optional subAccountId is not explained in either the schema or description.

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?

Clearly states the tool retrieves 'all open positions and account info' for a Drift account, using specific verb 'Get' and resource description. Easily distinguishes from sibling tools like adrena_getPositions (different protocol) and jupiter_getHoldings (different platform).

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?

Implied usage: use this tool to fetch Drift positions. No explicit guidance on when to use vs. alternatives, no exclusions or prerequisites mentioned.

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