research

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

Discloses that it searches 'filings, entities, and semantic index in parallel', which is key behavioral info. With no annotations, it carries full burden; it could be improved by stating it is read-only and has no side effects.

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?

Two sentences with no fluff. The first sentence states purpose and scope, the second gives usage hint. Every sentence 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?

Given no output schema and 3 fully documented parameters, the description adequately covers what the tool does and when to use it. It lacks output format details but that is acceptable for a search tool.

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 description adds context beyond the schema by explaining the 'agency' parameter's purpose with an example, and reinforces the focus parameter's optionality. Schema coverage is 100%, so baseline is 3; the extra guidance raises it.

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 is 'Primary research tool' that searches multiple sources in parallel, and specifies its use for any question. This distinctly positions it from sibling tools that are more specialized.

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?

Explicitly instructs to 'Use this FIRST for any question' and advises passing the agency parameter for agency-specific questions, providing clear when-to-use guidance. However, it does not explicitly mention when to switch to more specific tools.

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