get_sec_filings

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

With no annotations provided, the description carries full burden. It only states the basic action (get filings) but does not disclose data freshness, ordering, rate limits, or whether it returns full content or metadata. This is minimal for a data retrieval tool.

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?

A single, concise sentence that communicates the core purpose without unnecessary words. It is front-loaded and efficient, though a few additional details (like recency definition) would not hurt.

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 simplicity (1 param, no output schema), the description covers the basic what and for whom. However, it lacks definition of 'recent' and does not hint at output structure. Basic completeness but leaves unanswered questions.

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% (ticker described in schema). The description adds context by specifying 'for a stock ticker', which aligns with the schema. No additional meaning like format or examples beyond what schema provides, so baseline 3 is appropriate.

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 uses a specific verb 'Get' and identifies the resource 'SEC filings' with concrete filing types (10-K, 10-Q, 8-K, S-1). It clearly targets stock tickers, distinguishing it from sibling tools like get_market_data or get_xbrl_facts. However, 'recent' is ambiguous and could be clarified.

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?

There is no guidance on when to use this tool versus alternatives (e.g., get_xbrl_facts for detailed financial data). The description implies it's for recent filings but doesn't exclude other uses or provide context for selection among siblings.

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