portfolio_add_position

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

The description discloses the key behavior of averaging cost basis when ticker exists, but with no annotations and 7 parameters, more details on side effects or constraints would be beneficial.

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 concise with two short paragraphs, front-loading the purpose. No unnecessary words, but could be slightly more structured.

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 tool with 7 parameters and no annotations, the description covers the core action and averaging but omits details about portfolio existence or return values. Output schema exists, reducing need for return description.

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 coverage is 100%, so baseline 3. The description does not elaborate on parameters beyond the schema, offering no additional semantic value.

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 clearly states the tool adds a stock position, either new or increasing existing, with automatic cost basis averaging. However, it does not differentiate from the nearly identical sibling 'add_portfolio_position'.

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?

The description provides context on when to use (adding positions) and the averaging behavior, but lacks guidance on when not to use or alternatives like removing and re-adding for a different cost basis.

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