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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new context: real-time latency ('filings accepted minutes ago'), full history to 1994, the exact fields returned per row, and a per-filing price of $0.001, which is important cost information an agent cannot get from the schema.

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 action and resource, then scope, then row contents, ending with pricing. It is a single dense sentence carrying a lot of enumeration, which is borderline verbose, but nearly every clause adds usable information; the audience list is the weakest part.

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 9 optional parameters, no output schema, and no required inputs, the description does the necessary work by explaining what a returned row contains (company, CIK, ticker, form, filing date, acceptance time, item codes, links) and how far back data goes. Missing pieces are minor, mainly default sort/pagination behavior and whether empty filters return the whole market.

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 description coverage is 100%, so parameter semantics are already fully documented in the structured schema. The description mostly restates those filters in prose, adding only light interpretive value via 8-K item code examples (2.02 earnings, 5.02 officer changes, 1.01 material agreements) that the schema also lists. Baseline 3 is appropriate.

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 (Get) and resource (SEC EDGAR filings as clean JSON), enumerates the form families covered, and gives the scope (one company, watchlist, whole market) and historical depth (back to 1994). It does not, however, distinguish itself from close siblings such as sec_company_financials, sec_insider_trades or esef_annual_reports, so an agent still has to infer the boundary.

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?

Usage is implied through the scoping options ('for one company, a watchlist or the whole market') and the audience list (investors, news/alert services, compliance teams, AI agents), which hints at freshness-sensitive alerting use cases. There is no explicit when-to-use versus when-not guidance and no named alternative among the siblings.

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