wallet_positions

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

Discloses sorting by current value, returns compact form with omitted count, and that wallet may hold more than limit. No annotation provided, so description handles burden well.

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?

Two short paragraphs with an Args section. Every sentence adds value; no filler. Well-structured and easy to parse.

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?

Covers inputs and some output behavior, but lacks description of individual position fields (especially given no output schema). Vague 'compact form' leaves agent guessing the structure.

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 has 0% coverage; description adds full meaning: address accepts 0x address or nickname, limit is from 1 to 50 with default 15. Compensates completely.

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 'list a wallet's largest open positions by current value' with specific verb and resource. Distinct from siblings which are leaderboard, markets, overview, alerts.

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?

Explains inputs (address, limit) and output behavior (sorted, truncated with omitted count). No explicit when-not or alternatives to siblings, but context is clear.

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