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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, but the description adds substantial domain behavior beyond that: how short positions are represented with negative shares and cost basis, how cash is affected by short proceeds and dividends, and where realized P&L lives. This is exactly the kind of non-obvious accounting context an agent cannot infer from annotations or schema.

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 front-loaded with purpose, then domain-specific behavior, then an Args section. The short-position paragraph is dense but earns its place by clarifying non-obvious return semantics; it could be tightened slightly, but there is no filler.

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?

An output schema exists, so return fields do not need full re-explanation here, yet the description still adds essential accounting semantics for shorts, cash, and dividends. Together with read-only annotations and a single required parameter, an agent has everything needed to call the tool 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 description coverage is 0%, so the description must compensate for the single parameter. It only states 'portfolio_id: The portfolio UUID,' adding format information but not explaining where to obtain the UUID or any constraints. With one required parameter and no deeper semantics, a 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 states a specific verb and resource ('Get current holdings') and lists the exact data returned (quantity, cost basis, market value, unrealized P&L). It also distinguishes the tool from get_portfolio_statistics by noting that realized P&L belongs there, so an agent can tell the two apart without opening either schema.

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?

It clearly implies use for current position values and explicitly routes realized P&L questions to get_portfolio_statistics, which is a helpful alternative. It lacks explicit when-not-to-use guidance or a direct comparison to list_portfolios, so it falls short of a full 5.

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