list_filings

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

With no annotations, the description carries the full burden for behavioral disclosure. It reveals the ordering (newest first) and filtering capabilities, but does not explain the meaning of the required 'query' parameter, how limit/pagination works, or what the response contains. This leaves notable gaps for an agent.

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?

The description is two concise sentences, front-loaded with the primary action. Every word contributes information, with no redundancy or irrelevant detail.

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 5 parameters, no annotations, and no output schema, the description covers the core purpose and filters but leaves the required 'query' parameter undefined and does not mention 'limit' or return structure. It is adequate but incomplete for a smooth agent invocation.

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 schema has no parameter descriptions, so the description is the sole source of meaning. It explains 'forms' with examples, 'since'/'until' with date format, and implies 'query' is the company identifier. It omits 'limit', but overall it adds substantial semantic value beyond the raw schema.

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 clearly states the tool lists a company's filings, newest first, with explicit filtering by form type and date range. The verb 'list' and resource 'filings' are specific, and the 'newest first' adds scope that distinguishes it from related tools like search_filings.

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 provides clear context: use this when you need to list filings for a specific company, optionally filtered by form type or date range. It does not explicitly mention alternatives or exclusions, but the intended usage is evident from the description.

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