web_search

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It does not mention whether the tool is read-only, what kind of results it returns, any potential side effects, or limitations. The description simply restates the action without adding safety or behavioral context.

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 a single, short sentence that is appropriately sized and front-loaded. It contains no fluff or redundant words, making it easy for an agent to parse quickly.

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?

Although the tool is simple and has an output schema, the description lacks essential contextual information such as when to use it, what the query parameter entails, and any behavioral details. Given the absence of annotations and minimal parameter guidance, the description is insufficient for fully correct tool invocation in ambiguous situations.

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 and only one parameter, the description should explain what constitutes a valid query, any formatting requirements, or how the query is used. It only says 'about the given query,' which adds no meaningful detail beyond the parameter name and type.

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 performs a web search for the given query, using the specific verb 'search' and resource 'the web'. It implicitly distinguishes itself from sibling tools like github_search_repositories by specifying the web as the scope, but it does not explicitly name or contrast with alternatives.

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 offers no guidance on when to use this tool versus other sibling tools. It does not mention any preconditions, alternatives, or specific contexts, leaving the agent to infer usage only from the tool's name and generic purpose.

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