Filing detail

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

Discloses that the tool returns header metadata plus list of document files, which adds value beyond annotations. Annotations already declare readOnlyHint and openWorldHint, so no contradiction.

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 concise sentences, front-loaded with the action. Every sentence adds essential information: what it does, where to get inputs, and alternatives for other needs. No wasted words.

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 no output schema, the description adequately explains the return value (header metadata + document files). Additionally, it cross-references sibling tools for related tasks, providing complete context for an agent.

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% (baseline 3). Description adds context by explaining the role of accession number and providing examples (AAPL, 0000320193-24-000123), and notes that accession numbers come from stocks_filings.

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 it fetches one SEC filing's detail (header metadata + document files) with specific inputs. Distinguishes from siblings by noting that accession numbers come from stocks_filings and narrative text from stocks_sections/stocks_section.

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 (to get filing detail and document files) and when to use alternatives (stocks_sections/stocks_section for narrative text). Also directs to stocks_filings for accession numbers.

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