web_search

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

With no annotations, the description carries the burden. It discloses that the tool uses chat completions with web_search enabled and lists compatible models, implying it performs external web searches. However, it does not discuss safety, rate limits, or whether any modifications occur, though the non-destructive nature of search is assumed.

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 two sentences long, front-loaded with the primary purpose and followed by model options. No redundant information.

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 the output schema exists, return values are covered. The description provides model compatibility but lacks guidance on when to use this tool vs alternatives, which is a gap. Overall, it's adequate for a simple search tool.

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 0%, so the description must compensate. It partially does by specifying default and alternative model values for the 'model' parameter, but it does not explain the 'system_prompt' parameter or add format details for 'query' beyond the schema.

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 uses specific verbs 'Search / research' and identifies the resource as 'Grok2API chat completions with hosted web_search enabled', clearly distinguishing it from the sibling 'chat' tool by explicitly mentioning web_search.

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 implies usage by stating it's for search/research via chat completions with web_search, but it does not explicitly describe when to use this instead of other methods like the 'chat' tool. It provides model selection guidance but no exclusions or alternative suggestions.

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