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

Annotations already cover read-only, idempotent, non-destructive. The description adds the two things annotations cannot: a per-call cost ($0.01 USDC via x402 on Solana) and an alternate HTTPS endpoint, which materially changes how an agent should invoke and budget for it.

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 payload inventory and lookup keys lead, with payment and endpoint details trailing as short sentences. It is dense but every clause carries content; the long field enumeration is the only mildly bloated part.

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 does the work of enumerating return fields (CUSIP, ISIN, LEI, share counts, % of net assets, mix breakdowns) so the agent can judge whether the call answers its question. Only the nuance of 'latest' filing staleness is left unstated.

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% and both properties are already documented with their alias list and the 1-100 range, so the description's main addition is illustrative ticker values (VOO, QQQ, BND). That is a mild aid, not new semantic information — baseline 3 applies.

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 resource (mutual fund / ETF portfolio) and an authoritative source (latest public SEC Form N-PORT), plus the exact payload (holdings, mix, concentration, net assets, returns). This clearly separates it from SEC-adjacent siblings like sec_13f (institutional positions) and sec_financials.

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 names the lookup keys that select a fund (ticker, series id, class id) with worked examples, but never says when to prefer it over sec_13f, ticker_resolver or sec_edgar_search, and gives no exclusions. Usage is implied rather than routed.

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