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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the description's read-only nature adds no new safety info. The description does add that it returns 'current holdings' and the specific value fields, which is useful but not rich behavioral context like pagination, auth requirements, or data freshness.

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 concise sentence front-loaded with the action, followed by a minimal args line. No wasted words; every part earns its place.

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 simple single-parameter read-only tool with an output schema and safety annotations, the description is largely complete. It lacks usage guidance and any caveats, but the core purpose and parameter meaning are clear. Slight deduction for not mentioning when to prefer this over get_portfolio_statistics.

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?

With schema description coverage at 0%, the description compensates by explaining portfolio_id as 'The portfolio UUID', providing format and semantic meaning beyond the schema's bare 'Portfolio Id' title. This is sufficient for a single parameter, though it could explicitly state that it's the portfolio whose positions are retrieved.

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 a specific verb and resource: 'Get current holdings' with the exact fields included (quantity, cost basis, market value, unrealized P&L). This distinguishes it from siblings like list_portfolios (which lists portfolios) and get_portfolio_statistics (which likely returns performance metrics).

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?

There is no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or point to sibling tools for related tasks. The description only states what it does, leaving the agent to infer usage context.

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