Get Company Filings

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

Annotations already declare this as read-only, idempotent, and non-destructive, lowering the burden. The description adds useful context by specifying the return metadata (form type, filing date, document links) and the optional form-type filter, going beyond what annotations provide.

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 sentences, front-loaded with the main verb and resource, with no filler or redundant details. Every word 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?

The description covers the essential return information (metadata, form type, filing date, document links) since there is no output schema. It lacks pagination or limit details, but for a simple listing tool with only two parameters and strong annotations, it is sufficiently complete.

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% with both parameters clearly described in the schema. The description adds minimal new meaning beyond the schema—it repeats 'by CIK number' and provides additional form type examples (DEF 14A), but this does not significantly enhance the schema's existing parameter documentation.

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 action ('Get recent SEC filings'), the resource (filings by CIK number), and the return scope (metadata including form type, filing date, document links). It is specific enough to distinguish from financial metric or company overview tools, though it does not explicitly differentiate from the sibling '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 gives clear context for use (by CIK number, optionally filtered by form type) but offers no explicit guidance on when to use this tool versus alternatives like 'search_filings'. No exclusions or when-not-to-use scenarios are mentioned.

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