get_portfolio

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

No annotations provided, yet description lacks safety disclosures (read-only status, idempotency), rate limits, or caching behavior. 'Get' implies read access but doesn't confirm whether credentials are required or what happens if portfolio is empty.

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?

Front-loaded with clear purpose statement. Args section is compact and functional despite unconventional docstring formatting. No redundant text.

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?

Adequate for a single-parameter tool with output schema present. Missing behavioral context expected when annotations are absent. Does not mention default value in description text (though present in schema).

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?

Excellent compensation for 0% schema coverage: explicitly defines 'mode' parameter values ('shadow' for paper trades, 'live' for real trades). Could improve by noting the default value or that the parameter is optional.

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?

Clear verb ('Get') and resource ('portfolio positions and performance summary'). Implicitly distinguishes from sibling 'get_performance' by mentioning positions specifically, and from 'get_portfolio_strategy' by focusing on current holdings rather than strategy.

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 siblings like 'get_performance' or 'get_portfolio_strategy'. No explanation of when to prefer 'shadow' versus 'live' mode or prerequisites for accessing live data.

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