search_documentation

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

No annotations are provided, so the description must fully disclose behavior. It reveals that the search is naive keyword-based, that long queries fail, and that it returns full documentation pages. However, it does not mention response format, pagination, or what happens if no results are found, which are gaps for a retrieval 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 description is front-loaded with the purpose and follows with critical usage warnings in capitals. It could be slightly more concise, but every sentence adds value and the structure aids readability.

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 presence of an output schema, the description does not need to detail return values. It covers purpose, usage guidelines, and key behavioral traits. The tool is simple (1 parameter), and the description is sufficient for an agent to use it correctly.

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?

The input schema already provides a detailed description for the 'queries' parameter, but the description adds critical context: limit to 1-3 keywords, focus on unique terms, break complex questions. This goes well beyond the schema, teaching effective usage.

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 standard keyword search on Gemini API documentation, distinguishing it from siblings like get_capability_page (returns a specific page) and get_current_model (model info). The verb 'search' and resource 'documentation' are specific, and the mention of 'keyword search' differentiates it from semantic 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 provides explicit guidance: use short keyword queries (1-3 words), avoid long queries, break complex questions into separate simple queries. It does not explicitly state when not to use this tool versus alternatives, but the context implies it's for keyword-based documentation lookup, not for retrieving specific pages or model details.

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