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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the underlying source (SEC EDGAR full-text search API), the no-API-key requirement, and the $100M filing threshold that explains the data's scope. It does not, however, disclose pagination or result-size limits.

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-loads purpose, then a scannable bulleted when-to-use list, then a short capabilities/source footer. Efficient and well-organized, with only minor redundancy (the date-format note restating the schema).

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?

An output schema exists, so return-value explanation is not strictly required. The description covers purpose, scenarios, date filtering and source, which is sufficient to invoke the tool. The remaining gap is the absence of sibling differentiation and any mention of the internal fin-specific parameters.

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?

The description only adds semantics for three of the schema's parameters (query, start_date, end_date), and even the YYYY-MM-DD format note duplicates what the schema already says. The remaining parameters (wholesaler_ids, source_resource_id, exclude_fillers, optional_additional_filters, mcp_prompt_id) are never mentioned, so the description does not compensate for the low measured schema coverage.

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 ('Search SEC EDGAR for 13F-HR institutional holdings filings by institution name') and enumerates the returned fields (filing date, entity name, period of report, accession number). This clearly distinguishes it from the nearby sibling Get13FHoldings, which retrieves holdings rather than filing metadata.

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?

Provides an explicit 'Use this tool when' block with three concrete scenarios (fund/ETF holdings, investment strategy research, filing list over a date range). It is clear about when to use it, but never names an alternative sibling such as Get13FHoldings or GetEdgarCompanyFilings, so the boundary between this and the other EDGAR tools is left to inference.

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