sec_filing_search

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

Description reveals output (CIK number and filing page link) but lacks detail on side effects, network calls, or error conditions. No annotations provided, so transparency could be improved.

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?

Description is concise (4 sentences plus examples), front-loaded with purpose, and every sentence adds value. No redundant information.

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?

For a simple one-parameter tool with output schema, description covers purpose, parameter, and output summary with examples. Lacks error handling or edge case details, but sufficient for typical use.

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 defines symbol as string with no description. Description adds 'US stock ticker (e.g., AAPL, MSFT, GOOGL)', providing crucial context. Schema coverage is 0% so description fully compensates.

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?

Description clearly states purpose: 'Search SEC EDGAR for a company and get their filing page.' It distinguishes from sibling tool sec_filing by directing users to that tool for specific documents.

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?

Description explicitly tells when to use this tool (to get company filings page) and when to use sec_filing for specific documents. Also specifies argument as US stock ticker.

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