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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the SEC EDGAR data source, the non-affiliation disclaimer, and the pricing model ('$0.02 per successful call; failed calls are free'), which is behavior an agent cannot get from structured fields. Pagination/limit behavior is left to 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 core action and scope, followed by data source and price in compact sentences. No filler, though the price/disclaimer sentence is somewhat boilerplate-heavy relative to the tool's core purpose.

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 an output schema present, return values need not be explained, and the description covers source, cost, and lookup keys adequately for a read-only list tool. The main remaining gap is guidance on selecting this tool versus adjacent financial/data siblings.

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 all four parameters are documented in the schema itself, establishing a baseline of 3. The description reinforces the ticker-or-CIK duality and lists returned fields, but adds no syntax or format detail (e.g., amendment handling) beyond what the schema already provides.

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 ('List a US public company's recent SEC filings'), enumerates the form types covered, and names the lookup keys (stock ticker or CIK). An agent can distinguish it from company_financials or insider_trades without opening a schema.

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 description implies usage via 'by stock ticker or CIK' and the form-type scope, but never says when to choose this over siblings like company_financials or insider_trades, and states no exclusions or prerequisites. Usage is inferable but not spelled out.

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