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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety bar is low; the description adds genuinely useful context beyond that: paid access at $0.02 USDC per successful call via x402 on Solana, an equivalent HTTPS endpoint, and the fact that amendments and recent-filing links are included. It doesn't discuss rate limits or failure/refund behavior on unsuccessful calls.

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 what the tool returns, then how to address it, then pricing/endpoint. Dense but every clause carries information; the long parenthetical field list is justified because no output schema exists.

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 fully enumerates the returned fields and metadata, plus cost and transport details an agent needs before invoking. Nothing material is missing for a correct call.

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 each parameter already carries a description with examples and defaults, so the schema does the heavy lifting. The prose restates the lookup options (name/CIK/accession) and the aggregation/top-holdings semantics but adds no format or edge-case detail beyond the schema, which is the baseline-3 case.

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 (institutional holdings from a fund manager's latest SEC 13F-HR), the exact data shape (parsed EDGAR information table aggregated by CUSIP with issuer, class, shares, value, weight, put/call, voting authority), and filing metadata. This is clearly distinguishable from siblings like fund_holdings, sec_form4, sec_financials and sec_edgar_search.

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 concrete lookup modes: by manager name, by CIK, or pinned to an accession number, and the schema notes the default is the latest original 13F-HR. It doesn't explicitly compare against sibling SEC tools (e.g. when to use sec_edgar_search or fund_holdings instead), so it stops short of full routing guidance.

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