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

Annotations are empty, so the description carries the full disclosure burden. It reveals that results are scoped to 'the current user' and can be open-only or all, but says nothing about authentication requirements, defaults for open_only, pagination/limit behavior, result ordering, or what a position record contains.

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 tight sentences; the core action and mode come first, followed by filtering and usage triggers. No filler, though the parenthetical '(or all)' is slightly awkward phrasing.

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?

With no annotations, no output schema, and four parameters at 0% schema coverage, the description would need to explain result shape, pagination, and parameter defaults. It covers filters and intent only, so an agent still cannot predict the response or the meaning of `limit`.

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 0%, so the description must define all four parameters. It names the strategy ID and asset filters and hints at open_only via 'open (or all)', but never explains `limit` or states the default value of `open_only`, leaving half the parameters undocumented anywhere.

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?

States a specific verb and resource ('List ... positions') plus scope ('for the current user') and a default/mode distinction ('open (or all)'). It does not explicitly distinguish itself from the very similar sibling list_trades, leaving the agent to infer the difference between a position and a trade.

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?

Gives clear triggering conditions: 'when the user asks about their current positions, open trades, or what they are currently holding.' That maps directly to user phrasings, but there is no when-not guidance and no named alternative (e.g. list_trades) for overlapping requests.

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