search_docs

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

The description details the return format (titles, paths, excerpts) and parameter behavior (defaults, max results, source options). It does not mention rate limits or authorization, but as a search tool with no annotations, the description provides sufficient transparency.

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 concise and well-structured with bullet points for arguments. Every sentence adds value, and there is 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?

The description covers purpose, parameters, return value, and sibling tools. It could mention result ordering or pagination, but overall it is comprehensive for a search tool with an output schema.

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 description thoroughly explains each parameter: query with examples, max_results with default and maximum, and source with options and defaults. Since schema coverage is 0%, the description fully compensates by providing clear semantics.

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 'Search Google AI platform documentation' and specifies it returns matching pages with titles, paths, and excerpts. It distinguishes from sibling get_doc which is for reading full content.

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 on when to use this tool (searching documentation) and recommends an alternative (get_doc for reading full content). It also differentiates between documentation sources (geap vs vertex-ai).

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