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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the description adds genuine context beyond them: that funds are looked through to N-PORT holdings, that output is display-only and not a rating, and that the data is free under CC BY 4.0. It does not say what happens if neither optional parameter is supplied, nor anything about response size, latency, or rate limits for a potentially large holdings list.

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?

Front-loaded with the action and the two input modes, then the outputs. The long enumeration of return components is dense but justified because there is no output schema to carry it; only a mild cost in that the list of proprietary labels (Edgarette, Health Harbor boat, Cash Compass) is opaque to a first-time caller.

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?

With no output schema, the description usefully enumerates what comes back (warning share, concentration, sector mix, overlap, risks). Safety profile is carried by annotations. The remaining gap is behavioral edge cases: what happens with no arguments, and how a large holdings list is handled.

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 coverage is 100%, so the baseline is 3; the description earns an increment by specifying that the CIK belongs to a 13F filer such as a pension fund or manager and that fund inputs are resolved through to N-PORT holdings, which the schema does not state. It still leaves the cik-vs-holdings precedence and the weights-vs-dollar-amounts ambiguity to inference.

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 specific verb and resource ('Read a whole stock portfolio through SEC filings') and names both accepted input modes (13F filer CIK or a holdings list). The domain is unmistakable, though it never names the closest sibling (get_etf_health) or explains how a portfolio read differs from an ETF read, which is exactly where an agent could mis-route.

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?

Usage is implied by the input description ('give a 13F filer's CIK... or a list of holdings') and by 'Display only, not a rating', which clarifies what the tool is not. But there is no explicit when-to-use/when-not guidance relative to get_etf_health, watch_company, or get_company_performance, and no statement about whether cik or holdings should be preferred.

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