add_portfolio_position

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

The description mentions automatic cost basis averaging, a behavioral trait, but does not disclose side effects (e.g., overwriting existing position), authentication needs, or error conditions. With no annotations, the description partially meets the burden.

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, front-loaded with core action and key behavior. Efficient, though could benefit from structured elements like bullet points.

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?

Given the presence of an output schema and full parameter descriptions, the description provides core purpose and a key behavior. However, missing context about prerequisites and error handling leaves some gaps.

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 100%, so the baseline is 3. The description does not add parameter-specific meaning beyond the schema; 'automatic cost basis averaging' is general context.

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 'Add a position to your portfolio with automatic cost basis averaging' clearly states the verb and resource, including a key feature. However, it does not distinguish from the sibling tool 'portfolio_add_position', which appears to have similar functionality, causing potential confusion for the agent.

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 when-to-use or when-not-to-use guidance is provided. Prerequisites (e.g., portfolio existence) are not mentioned, and there is no comparison to alternatives like 'portfolio_add_position'.

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