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

Annotations already indicate readOnlyHint and openWorldHint, so the description adds context about EDGAR full-text search and the legal nature of 8-K filings. Yet it does not disclose potential limitations such as date ranges, pagination, or specific search syntax, which would be valuable for a search 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?

The description is concise, with two sentences that front-load the purpose and method in the first sentence and provide context and usage in the second. Every word adds value; no filler.

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 single-parameter tool with annotations covering safety and open-world behavior, the description is fairly complete: it states what it does, how to call it, and the meaning of 8-K. The lack of output schema and detailed return format is acceptable, though a note about result size or limitations would push it higher.

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 describes the single parameter 'url' as 'Company name, ticker, or keyword', and the tool description repeats this, giving clear semantics. However, the parameter name 'url' is misleading since it expects a search term, and the description does not provide examples or format details, so it doesn't add much beyond the 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 identifies the tool as retrieving SEC 8-K filings via EDGAR full-text search, with a specific resource and method. It also explains the nature of 8-K filings, distinguishing it from other extract_* tools, though it doesn't explicitly name an alternative.

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 implies usage for material event disclosures by defining 8-K, and provides a direct instruction to pass a company name, ticker, or keyword. However, it does not explicitly state when to prefer this tool over siblings like extract_finance or other SEC-related tools.

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