Analyze Portfolio Greeks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool 'analyzes' risk metrics, without explaining whether it executes trades, reads existing positions, aggregates multiple positions, or what side effects (if any) it has. This is too thin for safe invocation.

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 a single sentence with no filler or redundant elaboration. It is front-loaded and appropriately brief, though the brevity contributes to the lack of necessary detail elsewhere.

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 one required nested parameter at 0% schema coverage and no annotations, the description is far too thin. Although an output schema exists, the agent still lacks essential input-construction guidance and cannot confidently call the tool. This is materially incomplete for a portfolio-analysis tool.

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 0%, and the description adds no meaning about the portfolio_data parameter. The schema only says 'Portfolio positions data' with additionalProperties allowed, and the description does not clarify the expected structure, required fields, or data format. An agent cannot reliably construct a valid portfolio_data object.

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 uses a specific verb ('Analyze') and identifies a clear resource ('portfolio Greeks and risk metrics for options positions'). It is clear enough to be distinguished from sibling tools focused on individual strategies like analyze_straddles or analyze_spreads, though it does not explicitly differentiate itself from analyze_portfolio_strategies.

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 gives no guidance on when to use this tool versus alternatives. It does not state conditions such as 'use this for portfolio-level risk, not single-position strategies' or mention any exclusions, leaving the agent to infer usage from the name alone.

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