gp_discover_companies

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

No annotations provided. Description does not disclose behavioral traits such as side effects, permissions, rate limits, or return characteristics. With no annotation support, the description should cover safety and behavior but falls short.

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?

Single sentence, no waste. Front-loaded with action and object. Could benefit from a second sentence (e.g., return format) without losing conciseness.

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 does not mention what is returned (list of companies, IDs, etc.). For a discovery tool, this is a significant gap. The description is too terse for an agent to understand full invocation impact.

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 is 100%, so the schema documents all parameters. However, the description adds minimal semantic value beyond 'matching the campaign parameters'. No explanation of how each field (e.g., maxEmployees, targetIndustry) modifies the search.

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 uses verb 'Searches for and discovers' with resource 'target companies', giving a clear purpose. It distinguishes from siblings like gp_research_company (which researches specific companies) but could be more specific (e.g., 'discovers new companies from campaign parameters').

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 (e.g., gp_research_company for existing companies). No explicit when-to or when-not context. Only inferred from tool name.

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