Get Filing Document

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

Discloses that filings can be very large (10-K up to 1MB+) and explains truncation behavior via maxLength, including the truncated boolean in the response. This provides behavioral benefits beyond the readOnlyHint annotation, which already indicates no side effects.

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?

Three sentences, no redundancy. The first sentence states the core purpose, followed by size warning, preview guidance, and response fields. Every sentence adds value.

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 the output schema exists, the description sufficiently covers return fields and behavior. With only 2 parameters and clear annotations, the description is complete for an AI agent to invoke correctly.

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 covers both parameters (filingId, maxLength) with basic descriptions. The tool description adds value by clarifying filingId is numeric and must come from search_sec_filings, and that maxLength triggers a truncated boolean in the response. It enriches the schema but could be more explicit about expected formats.

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 retrieves raw text/HTML content of an SEC filing by its internal filing ID, specifying the verb (Get), resource (filing document), and key context (returns company_name, form_type, etc.). This distinguishes it from sibling tools like search_sec_filings or get_exhibit_content.

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 advises to find filing IDs using search_sec_filings first and mentions maxLength for previews. While not listing alternatives or when-not-to-use, this guidance is clear and contextually sufficient given the sibling tools.

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