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. It adds a useful behavioral trait: filings are pre-processed with an LLM to produce supply chain signals, sentiment, and material mentions, rather than returning raw filings. However, it does not mention rate limits, permissions, pagination behavior, or whether results are read-only, leaving significant gaps 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 a single compact sentence with no filler or repetition. It front-loads the core resource (SEC EDGAR filings) and the value-add (LLM processing for supply chain signals). While it is short relative to the tool's complexity, it is not bloated and earns its place.

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?

This is a complex tool with 10 parameters, no output schema, and no annotations. The one-sentence description is insufficient: it does not explain how the fields combine (e.g., are filters ANDed?), what the returned data structure looks like, or how to interpret the LLM-extracted signals. The rich parameter schema compensates for filter meanings but not for overall tool behavior and result expectations.

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 description coverage is 100%, so the baseline is 3. The description does not add parameter-specific details beyond what the schema already provides, though it introduces the key concepts (supply chain signals, sentiment, material mentions) that map to the `sentiment` and `material` parameters. This adds minimal semantic value but does not compensate for any missing schema info.

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 tool name 'search_sec_filings' and description identify the resource (SEC EDGAR filings) and the function (extract supply chain signals, sentiment, and material mentions via LLM processing). It is clearly distinct from sibling tools that cover funding, trade flows, mineral deposits, and regulatory signals. However, the description itself does not explicitly state the verb 'search' or 'query', relying on the tool name to imply the action.

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 such as search_regulatory_signals or search_mineral_deposits. There is no mention of exclusions, prerequisites, or complementary tools. Usage context is only implied by the resource type (SEC filings), which is weak guidance for an agent choosing among sibling search tools.

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