list_filed_documents

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

No annotations provided, and the description only notes grouping by category. It lacks details on error handling, pagination, or read-only nature, leaving behavioral traits largely unspecified.

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?

Two sentences efficiently convey purpose and usage of results, though adding parameter details would improve conciseness without bloat.

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?

Given 3 parameters with 0% schema description, no output schema, and no annotations, the description is insufficient. It fails to explain parameters or return structure, leaving the agent underinformed.

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 0% and the description gives no explanation for 'company', 'match', or 'result_index'. The agent receives no guidance on how to provide valid input beyond the schema structure.

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 'List the documents filed for a company' and distinguishes from sibling fetch tools by indicating this is for listing, not downloading.

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 tells when to use this tool (listing) and directs to 'fetch_filed_document' or 'get_shareholders' for downloading, effectively differentiating from siblings.

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