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

With no annotations, the description carries the full burden. It does disclose a valuable behavioral trait: the source of truth differs by account mode, so live positions reflect venue state while paper positions are derived from fills — this warns the agent the numbers may not match local records. It says nothing about freshness, failure modes, or what happens when no positions exist.

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 clause with the resource first and the mode distinction in parentheses. Every word earns its place with zero preamble or filler.

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?

No parameters or annotations means less to cover, but there is also no output schema, so the description is the only place return values could be characterized — and it says nothing about what a position record contains (size, entry price, unrealized PnL, venue). Adequate for identification, thin for interpretation.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. Nothing in the description is needed to compensate for schema gaps.

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 the resource clearly ('Open positions') and adds a meaningful discriminator the name alone doesn't convey: where the data comes from in each mode (live = venue truth, paper = from your fills). It is not explicitly differentiated from siblings like list_orders or get_account, but the mode-based provenance note does real work.

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 when-to-use or when-not-to-use guidance, and no alternative is named. An agent deciding between this, list_orders, and get_account gets no routing signal from the description beyond the implied 'look at open positions' reading.

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