data_get_positions

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

With no annotations provided, the description must convey behavior. It implies a read-only query by 'fetch current positions,' but does not explicitly state idempotency or side effects. Still, it is clear and sufficient for this type of 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?

The description is moderately concise, containing multiple sentences but each serving a purpose: definition, usage, input format, and next steps. It is front-loaded with essential information.

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?

Given the tool's simplicity (one parameter, with output schema), the description covers all necessary aspects: what it does, when to use it, input format, and typical follow-up actions. It is complete for an agent's decision-making.

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 only parameter is 'user' within 'args'. The schema describes 'args' as 'Wallet query arguments' but not 'user'. The description adds value by specifying the format ('wallet address, typically in 0x... format'), compensating for the schema's lack of detail.

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 clearly states 'Fetch current positions for one wallet,' specifying the verb, resource, and scope. It distinguishes from siblings like 'data_get_closed_positions' and 'data_get_activity' by focusing on current positions.

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?

Provides explicit when-to-use ('know what a wallet currently holds'), when-not-to-use ('if you still need to discover which market exists'), and an alternative tool ('prefer over get_activity'). This offers clear guidance for an AI agent.

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