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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context (SEC EDGAR data API, no API key required) but omits behavior that matters for EDGAR: rate limits, whether "every filing on record" is truncated or paginated, and what happens if no CIK is supplied (cik defaults to null).

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 core action and scope, then a short scannable bullet list of use cases, then source/provenance notes. No sentence is filler, and the CIK-lookup URL is placed where the agent will need it.

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 need not be described, and the source/no-key note is helpful. But with zero required parameters (cik defaults to null) and six undocumented optional parameters, an agent cannot tell whether the tool is callable with no arguments or how the filter parameters alter the query — a meaningful completeness gap.

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?

Only cik is addressed, and even that duplicates the schema (zero-padding, where to find a CIK). The remaining parameters — wholesaler_ids, source_resource_id, exclude_fillers, additional_display_fields, optional_additional_filters, mcp_prompt_id — are unexplained in the description, and several are unrelated internal-fintech plumbing whose interaction with an EDGAR filings query an agent cannot infer. With the supplied coverage signal at 0%, the description needed to compensate and does not.

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 ("Retrieve all SEC filings for a company or institution using its CIK") and enumerates the returned fields (form type, date, accession number, description). It is clearly distinguishable from lookup-type siblings like LookupTicker or SearchEdgar13F because it declares the scope as "every filing on record" for one CIK.

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 explicit "Use this tool when:" block gives three concrete situations (have a CIK, track 13F/ADV/ownership history, need accession numbers), which is stronger than implied usage. However, it never names the alternatives or states when NOT to use it — notably SearchEdgar13F for 13F-specific searches, a sibling an agent could easily confuse with the "track 13F" bullet.

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