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

Annotations only cover the safety profile (readOnly, openWorld, non-destructive); the description adds substantive behavior: source is SEC EDGAR full-text search, covers NPORT-P and NPORT-P/A, filing cadence is within 60 days of month-end, and v1A returns metadata only with per-holding detail living in the linked XML. This goes well beyond what the annotations disclose.

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?

It is long but dense and front-loaded, leading with the resource definition before use cases and return shape. Every paragraph earns its place, though the volume is on the heavier side for a single tool description.

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 carries the return-value burden and does so fully: it lists the metadata fields returned (filer trust name + CIK, period_ending, filing type, file number, state, and primary_doc.xml URL) and directs agents to the XML for security-level data. Nothing needed to call it correctly is missing.

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, but the description adds real semantics: it explains that period_ending identifies which month the report covers (vs file_date), and clarifies the NPORT-P vs NPORT-P/A amendment distinction behind is_amendment. It does not add much for the remaining params, but it does exceed the schema-only floor.

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 states a specific verb+resource (returns SEC Form N-PORT monthly portfolio reports from registered investment companies) and defines the domain (mutual funds, ETFs, closed-end funds). It explicitly differentiates itself from the closest sibling, get_institutional_holdings (13F), by contrasting manager-level vs fund-level and quarterly vs monthly.

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 enumerates concrete when-to-use scenarios ('recent fund portfolio filings', 'when a specific fund family last reported', 'bridge from a fund trust name to primary_doc.xml') and names the complementary tool. The routing decision is explicit rather than inferred.

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