positions

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

No annotations provided. Description says 'Gets', implying a read operation, but does not explicitly state read-only behavior, authorization requirements, or any side effects. Lacks disclosure of data freshness or scope.

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?

Single sentence with six words, no waste. Clearly communicates purpose without extraneous information.

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 parameterless tool with an output schema, the description provides adequate context about return values (quantities and values). Could mention data recency or scope, but overall sufficient.

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?

No parameters exist, so the schema covers all aspects. Baseline 4 is appropriate as the description does not need to add parameter information.

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?

Clearly states it gets current stock positions with quantities and values. Distinguishes from sibling tools like 'portfolio' or 'all_option_positions' by specifying 'stock positions', implying equities only. However, no explicit differentiation from similar tools.

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 on when to use this tool versus alternatives such as 'portfolio', 'aggregated_portfolio', or 'all_option_positions'. The description does not provide context on prerequisites or typical use cases.

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