get_open_positions

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

With no annotations, the description must carry the full behavioral burden. It only says 'Pulls,' implying a read operation, but gives no details about the return structure, authentication requirements, or side effects. The phrase 'positions and holdings summary' adds some scope but is ambiguous about whether it returns individual positions, a summary, or both.

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?

The description is a single sentence with no filler. It is concise and front-loaded, communicating the core action and resource efficiently.

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?

The tool is simple and has an output schema, so return values are covered there. However, the description does not mention any prerequisites (e.g., an authenticated Webull account) or clarify the difference between 'positions' and 'holdings summary.' It is minimally adequate but leaves room for ambiguity.

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 input schema has zero parameters, so schema coverage is complete. The baseline of 4 applies because the description has no parameter information to add, and no parameters exist to confuse.

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 states a specific verb ('Pulls') and a specific resource ('open Webull account positions and holdings summary'). This clearly distinguishes it from sibling tools like get_open_orders (orders) and get_account_info (account details), as it focuses on positions/holdings.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of scenario, prerequisites, or exclusions, and no reference to sibling tools that might be better suited for related queries.

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