search_sec_filings

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only lists arguments. It does not mention return format, whether results are metadata or full text, pagination behavior, rate limits, or data source specifics, making behavioral expectations unclear.

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 appropriately sized: one clear purpose sentence followed by a compact, information-dense Args list. Every sentence contributes value and there is no redundancy or fluff.

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 that an output schema exists and this is a relatively simple search tool, the description adequately covers the purpose and all parameters. However, it lacks usage alternatives and behavioral context, so it is not fully complete for an agent deciding among sibling tools.

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?

The schema has no property descriptions (0% coverage), so the description effectively compensates by documenting all three parameters with meaningful details: an example for ticker, a list of accepted form_type values, and a range for limit. This goes well beyond the bare schema.

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 searches for SEC filings for a company, with a specific verb and resource. However, it does not explicitly distinguish itself from sibling tools like get_filing_sections, which also deals with SEC 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 provides no guidance on when to use this tool versus alternatives, no exclusions, and no contextual hints beyond the basic purpose. It lacks any mention of when to prefer search_sec_filings over tools like get_filing_sections or get_company_facts.

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