portfolio_summary

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

Describes the outputs and inputs sufficiently for a read-only analysis tool. No annotations exist, so description carries burden; it does not mention auth needs, rate limits, or side effects, but given the nature of the tool, it is adequately transparent.

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?

Two sentences: first states purpose, second adds details and constraint. Every sentence is necessary and no fluff.

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 relatively simple input, the description fully explains what the tool does and provides a constraint. It covers inputs, outputs, and limits, making it complete for an AI to select and 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?

Only one parameter (holdings) with 100% schema coverage. Description echoes the schema by mentioning 'holdings with buy price and quantity' but adds no further semantic detail beyond what is in the 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?

Clearly states it analyzes a stock portfolio with specific inputs (holdings, buy price, quantity) and outputs (current value, P&L, allocation, gain/loss per holding). Distinguishes from sibling tools like get_quote or compare_stocks.

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?

Describes when to use (analyze a portfolio) and includes a constraint (max 20 holdings). Does not explicitly mention when not to use or suggest alternatives, but the use case is clear and distinct from siblings.

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