analyze_portfolio

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

No annotations provided, so description carries full burden. Discloses 'informational only', 'No investment recommendations', max 50 positions constraint, and return fields (value, allocation, HHI, warnings). No contradictions.

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?

Description is moderately concise and structured: purpose sentence, parameter list, return description, disclaimer. Could combine some lines, but all sentences add value.

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 no output schema and moderate complexity (2 params, one nested), description covers purpose, parameters with constraints, returns, and usage caveats. Sufficient for an agent to invoke correctly.

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 0%, but description adds significant meaning: explains holdings as 'Mapping of ticker symbol to amount held' with example and max 50 positions; clarifies vs_currency default. These details go beyond the raw schema.

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?

Description clearly states 'Value a portfolio and flag concentration risk', a specific verb+resource. Differentiates from sibling tools (get_price, get_market_history, search_knowledge) by focusing on portfolio analysis rather than price retrieval or market history.

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?

Description implies use for portfolio valuation and concentration risk assessment. Does not explicitly state when not to use nor name alternatives, but the purpose is clearly distinct from siblings.

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