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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results come from a positions cache, which signals possible staleness, but it omits error behavior for an invalid/empty wallet, any rate-limit or auth context, and what an empty result looks like.

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?

A single front-loaded sentence with zero filler; the resource and its data source appear immediately.

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?

For a simple read tool with full schema coverage this is adequate, but with no output schema and no annotations, the description could still state what a position record contains or how many come back by default. The cache note helps but leaves real gaps.

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 100%, so the wallet format, the limit default/max, and notification_message are already documented. The description adds only the 'Polymarket wallet' framing and nothing about pagination behavior of limit, so the baseline 3 applies.

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 pairs a specific verb ('Returns') with a specific resource ('current open positions for a Polymarket wallet') and names the upstream data source, so an agent can tell it apart from sibling read tools like get_position_transfers or get_trader_activity. It stops short of explicitly contrasting itself with those siblings, keeping it below a 5.

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?

There is no guidance on when to choose this tool over get_position_transfers, get_wallet_transfers, or get_trader_activity, and no stated prerequisites (e.g., whether the wallet must be a Polymarket trader). The 'current open positions' phrasing implies usage but names no alternatives or exclusions.

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