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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful operational context ('SEC EDGAR full-text search API. No API key required'), but says nothing about result caps, pagination, or what an empty/no-match response looks like.

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 the verb, resource and return fields, then a scannable bullet list of use cases. The sentence about the $100M filing threshold is domain color rather than tool guidance, and is the only sentence that does not directly earn 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?

An output schema exists, so return values do not need explaining, and annotations cover safety. The description covers purpose, use cases, date format, source and auth, leaving only minor gaps (behavior when query is omitted, result limits) for what is a simple search tool.

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 restates the start_date/end_date YYYY-MM-DD format and implies the query is an institution name, both of which are already fully documented in the schema. The many internal parameters (wholesaler_ids, source_resource_id, exclude_fillers, mcp_prompt_id) are never mentioned in the description, so this section is useful but partial.

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 ('Search SEC EDGAR') and resource ('13F-HR institutional holdings filings') and further specifies the search key ('by institution name') plus the returned fields (filing date, entity name, period of report, accession number). This implicitly separates it from the sibling Get13FHoldings (which returns positions, not filings), but no sibling is named explicitly.

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?

Three explicit 'Use this tool when:' bullets cover the core scenarios (portfolio lookups, strategy research, date-ranged filing lists), which is well above implied usage. It stops short of saying when not to use it or naming Get13FHoldings as the alternative for position-level data.

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