portfolio_get_my_portfolio

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

No annotations are provided, so the description carries full burden. It mentions key behaviors (returns positions, cost basis, market values if available, P&L, performance metrics) but does not disclose whether it reads only, requires authentication, or has any side effects. The 'if prices available' caveat is helpful.

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 relatively concise at about 80 words, split into two paragraphs. It front-loads the purpose and uses bullet points for clarity. Some minor redundancy could be trimmed, but overall efficient.

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 the tool's low complexity (3 optional parameters), the description is reasonably complete. It covers the main data returned. However, it could mention any limits on length or performance implications of fetching live prices.

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?

All three parameters have descriptions in the input schema (100% coverage). The description adds no additional parameter-specific meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 clearly states the tool retrieves a complete portfolio with positions and performance metrics, listing specific data included. However, it does not explicitly differentiate from similar sibling tools like get_my_portfolio or portfolio_get_my_portfolio, leaving ambiguity about when to use this one over others.

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 vs alternatives. The description does not specify prerequisites, exclusions, or scenarios where other tools might be preferred. Given the many portfolio-related siblings, this is a notable gap.

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