Get Filing Document

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

Annotations declare readOnlyHint=true, and the description adds valuable behavioral context: files can be very large (1MB+), maxLength truncation behavior, and response includes a 'truncated' boolean. No contradiction with annotations.

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 with front-loaded key purpose, followed by size warning and parameter usage. Every sentence provides necessary information without redundancy.

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 a detailed output schema mentioned (and likely containing the listed fields), the description covers all needed context: how to get the ID, size behavior, truncation, and response contents. Adequate for a two-parameter tool.

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 baseline is 3. The description does not add new input parameter details beyond what the schema already provides (e.g., filingId and maxLength descriptions are identical). The mention of response fields (company_name, etc.) is output-related, not parameter semantics.

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?

Clearly states verb (Get), resource (full raw text/HTML content of an SEC filing), and identifier (internal filing ID). Distinguishes from siblings like get_filing_exhibits and search_sec_filings by specifying it returns the complete document.

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 instructs to find filing IDs using search_sec_filings first, and suggests using maxLength for previews. Provides clear context but does not explicitly state when not to use this tool (e.g., for exhibits).

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