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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the bar is lower. The description adds two things annotations cannot: the newest-first ordering and the semantic warning that results are quarterly snapshots rather than discrete trades, which materially affects interpretation. It stops short of describing pagination behavior despite the cursor parameter.

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?

Two sentences, no filler, and the scoping/ordering fact is front-loaded before the semantic caveat. Every sentence earns its place.

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 would ideally indicate what a disclosure record contains (fund identity, filing date, holdings summary) so the agent knows what it will receive. Sorting and snapshot semantics are covered, but return shape and pagination expectations are left entirely to the schema.

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%: all four parameters carry descriptions with ranges, defaults, and format examples (e.g., 2026-Q1, meta.next_cursor). The description adds no parameter-level detail beyond ordering, so the 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?

The description names a specific resource (13F disclosures) with scope (fund level) and ordering (newest first), so the agent knows exactly what is listed. It does not, however, distinguish itself from close siblings like institutional_list_holdings or institutional_get_fund_holdings, so sibling differentiation must be inferred.

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?

The clarification that this is a quarterly snapshot stream rather than a feed of single trades implies when the tool is appropriate, which is genuinely useful. But there is no explicit when-to-use statement and no named alternative (e.g., institutional_get_fund_holdings) for retrieving a specific fund's positions.

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