web_search_autocomplete

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

With no annotations, the description must disclose behavioral traits, but it only explains the operation dispatcher pattern and required query. It does not mention whether the operation is read-only, any rate limits, or what the response format looks like, leaving the agent without important 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 compact and front-loaded with the purpose, but the bullet 'autocomplete (required: query): Autocomplete' includes a redundant trailing 'Autocomplete.' Overall, it is well-structured and efficient with no unnecessary filler.

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?

For a single-operation tool, the description covers the dispatcher pattern and the required parameter, but it lacks any mention of the response structure or behavior for edge cases like empty queries. Given the absence of an output schema, this omission is noticeable, though the tool's simplicity keeps the gap moderate.

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 schema describes the operation and args generically, but the description adds the specific required parameter 'query' and states that it is mandatory for the autocomplete operation. This clarifies the invocation beyond the schema, though it could elaborate further on the query's expected format.

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 'Google search autocomplete / query suggestions for a partial query,' which is a specific verb+resource combination. It distinguishes this tool from sibling search tools by focusing explicitly on query suggestions rather than general search or other specialized features.

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 for partial query autocomplete but does not explicitly state when to use this tool versus alternatives like realtime_web_search or google_ai_mode. There are no exclusions or alternative recommendations, so the agent must infer the appropriate context.

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