get_portfolio_analysis

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by disclosing that holding/account names cannot be decrypted on stdio (Stream D Phase 4 limitation) and that account/account_id filters are ignored on this transport. This goes beyond the annotations to set transport-specific expectations.

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 concise sentences. The first sentence immediately states the core purpose. The second adds critical transport-specific limitations with no redundant or extraneous content.

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 lack of output schema, the description should ideally outline return fields or behavior. It covers the main purpose and a key limitation, but omits details about the 'symbols' parameter's effect, what allocation breakdown entails, and the response structure. Adequate for a simple read-only tool but with gaps.

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 75% schema coverage, baseline is 3. The description notes that account and account_id are unused, but does not clarify the purpose of the 'symbols' parameter (which lacks a schema description) or provide additional semantics for reportingCurrency. The description adds no meaning beyond what the schema already provides.

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 'Portfolio holdings with allocation breakdown' which specifies the verb (get/retrieve), resource (portfolio holdings), and output (allocation breakdown). It distinguishes from siblings like get_portfolio_performance, analyze_holding, and trace_holding_quantity by focusing on current holdings and allocation rather than performance or deep analysis.

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?

Explicitly tells when not to use this tool on stdio ('use HTTP MCP or the web UI for this query') and notes that account/account_id filters are unused on this transport, guiding agents to alternative tools or transports for decrypted names or account-specific queries.

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