List a company's SEC filings

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

With no annotations, the description carries the behavioral disclosure burden. It discloses ordering (newest first), internal ticker/company resolution, and the fact that unfiltered results are dominated by Form 4 filings. It does not explicitly state read-only behavior or return format, but 'List' makes this reasonably clear.

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?

Four concise sentences, each with a purpose: action/scope, usage context, company resolution, and filtering guidance. No wasted words, and the most important information is front-loaded.

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?

For a simple list tool with three well-documented parameters, the description covers selection criteria, invocation behavior, and filtering advice. It does not describe return fields, but with no output schema the agent can still reasonably infer it returns a list of filings. Slightly more detail on return shape would make it fully complete.

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 coverage is 100%, so the schema already documents company, forms, and limit, including the Form 4 warning. The description reinforces the ticker/company resolution and filter-by-form guidance, but does not add substantively new parameter semantics beyond what the schema 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?

The description opens with 'List filings a specific public company submitted, newest first,' which clearly identifies the resource and operation. It also distinguishes itself from the sibling search_filings by contrasting recent-reports-by-company with word-based searching.

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?

Explicitly states when to use the tool: 'Use when the user names a company and wants its recent reports rather than searching for particular words.' It also gives practical guidance on filtering by form type, which helps the agent decide how to invoke it appropriately.

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