madeonsol_wallet_positions

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

Annotations already indicate readOnly=true, openWorld=true, idempotent, non-destructive. The description adds that it shares the /pnl cache (performance implication), mentions live price source (mc-tracker, null if delisted), and notes PRO+ tier access. Could still mention what happens if wallet has no positions or rate limits, but provides useful context beyond annotations.

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?

Description is a single paragraph that front-loads purpose, lists fields efficiently, and is reasonably concise. Could be slightly more structured (e.g., bullet points for fields), but no unnecessary sentences.

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 has no output schema, the description provides the field list which is helpful. However, it omits behavior for wallets with no positions, error cases, or limits on the number of positions returned. For a simple tool, the description is almost complete but missing a few edge-case details.

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% (1 parameter, address), and the description does not add meaning beyond the schema description. The parameter is straightforward, so baseline 3 is appropriate.

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 it returns open positions for any wallet, explicitly distinguishes it from the sibling tool madeonsol_wallet_pnl by noting it is a lighter slice for use cases not needing the full PnL summary or curve. The verb 'positions' and resource 'wallet' are specific.

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?

Description explicitly says when to use ('for use cases that don't need the full PnL summary or curve') and references the alternative madeonsol_wallet_pnl, providing clear usage guidance.

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