company_research_v2_search_companies

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

No annotations provided; description adds 'Extracts filters' implying parsing behavior but no details on safety, rate limits, or side effects. Adequate but not rich.

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?

Very short single sentence, no wasted words. Could benefit from slight expansion for clarity, but appropriately concise.

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?

No output schema and description omits return format (e.g., company fields, pagination details). Without this, agent cannot effectively use results. Among sibling tools, lacks relational context.

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 coverage 100% so baseline 3. Description adds minimal extra meaning beyond schema (only mentions filter extraction for query parameter). No additional semantics for page, page_size, or output_variable_name.

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?

States 'Search for companies using natural language query' with specific verb and resource. Mentions filter extraction, differentiating from generic search tools, but doesn't explicitly distinguish from sibling company research search tools.

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?

No guidance on when to use this tool vs alternatives like `company_research_v2_run_full_research` or `get_search_results`. Lacks context for tool selection among many siblings.

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