research

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

The description adds minimal behavioral context beyond the annotations (readOnlyHint, openWorldHint). It states the tool returns both search results and fetched content, but does not disclose details like the number of top results fetched, caching behavior, or potential rate limits.

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 extremely concise (10 words) and front-loaded, but it sacrifices necessary detail. While brevity is valued, the lack of parameter or usage information makes it incomplete.

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 13 parameters, no schema descriptions, and an output schema, the description is critically incomplete. It fails to explain parameter roles (e.g., 'depth' controls paging, 'engines' selects search providers) or the structure of the returned data beyond 'both'.

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?

With 0% schema description coverage, the description must explain parameters. However, it mentions no parameter details—'search the web, fetch the top results, return both' gives no insight into the 12 optional parameters (depth, engines, cache, domains, etc.) or their purposes.

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 it performs a combined search and fetch operation ('search the web, fetch the top results, return both'), distinguishing it from siblings like 'search' (which likely only returns results) and 'fetch' (which fetches a given URL).

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 its siblings. There is no mention of alternative tools, prerequisites, or exclusions, leaving the agent to infer from context.

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