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

With no annotations, the description carries the full burden. It explicitly states 'Read' and 'Display only, not a rating' indicating a non-mutating, informational operation. It discloses internal behavior (funds looked through to N-PORT holdings) and licensing (CC BY 4.0). Missing details like handling when both CIK and holdings are provided, or error conditions, but these are minor for a display-only tool.

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 detailed but every sentence adds value: purpose, input modes, inner workings, output list, and caveat. It front-loads the core purpose. It could be trimmed slightly (e.g., listing all metrics is long) but remains efficient for the information density.

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 read-only tool with two optional parameters and no output schema, the description is quite complete. It names the input modes, explains the transformation, and enumerates the output metrics. It leaves out error handling and edge cases (e.g., malformed holdings), but these are typical and not necessary for correct invocation.

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 100%, so baseline is 3. The description adds meaning beyond schema by clarifying the either/or relationship (CIK or holdings) and the interpretation of holdings (ticker and weight). It also explains that funds are looked through to N-PORT, which affects how holdings are processed. This raises it above baseline.

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?

States a clear verb (read) and resource (whole stock portfolio via SEC filings). Distinct from siblings like get_etf_health (portfolio vs ETF) and get_company_performance (single company vs portfolio). The description lists many specific metrics, removing ambiguity about what the tool does.

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?

Gives context that it reads portfolios via CIK or holdings, but does not explicitly state when to prefer this over siblings like get_etf_health or get_company_performance. It implies usage for portfolio-level health analysis but leaves exclusion conditions implicit. The 'Display only, not a rating' clarifies it is not a rating tool, but no alternative tool is named.

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