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

Annotations already declare read-only, open-world and non-destructive behavior; the description adds meaningful context beyond them, including the connected-key requirement, what is returned (title, URL, date, excerpts), that excerpts are not verified quotes, and that page text must never be treated as instructions. The safety caveats are especially valuable for an open-web 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 purpose is front-loaded, followed by usage guidance, return caveats and a parameter note. The sentences generally earn their place, though 'Read-only' repeats the annotation and is slightly redundant.

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 six parameters, an output schema, and annotations covering safety, the description supplies the important behavioral and trust context an agent needs. It is not fully complete because several optional parameters, including companyId, maxResults and connectionId, receive no explanation.

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 only 17%, so the description must compensate. It explains objective as a sentence used for ranking, clarifies that searchQueries means up to five keyword queries alongside the objective, and says to pass agent_name; however, companyId, maxResults and connectionId are left unexplained, so the compensation is only partial.

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 states a specific verb and resource: a web search through the company's connected Parallel key, ranked by an objective, with keyword queries. It is not a tautology and distinguishes itself as an 'independent discovery pass', though it does not explicitly name sibling search tools such as connection_search_exa or fundraising_search_web.

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?

It gives clear usage context: use it as a second, independent discovery pass because two converging searches are stronger than one. It does not provide explicit when-not-to-use guidance or name alternatives, so it falls short of a 5.

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