maps_zoom_search

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

Given no annotations, the description carries full responsibility for transparency. It discloses the exact zoom level, the restriction on direction ('in|out'), the revalidation of expectedQuery, and the success criteria (same query and URL change). This gives a clear behavioral contract, though it could be more concise.

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 overly verbose and repetitive, with phrases like 'exactly one level', 'exact-one level', and 'exact one-level' repeated. It could be condensed to a couple of sentences without losing meaning. The structure is functional but not polished.

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 provides essential context: the tool operates on the active search-result viewport, requires an enabled interactive map, and defines success via URL change. It doesn't describe return values (no output schema), but that's not required. It is complete for a simple zoom action.

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?

Both parameters are touched upon: direction is clarified as restricted to 'in|out', and expectedQuery is described as the search query to be preserved and revalidated. This adds semantic meaning beyond the bare schema, covering both parameters adequately.

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's function: zooming the Google Maps viewport by exactly one level while preserving a search query. It distinguishes from sibling tools (search, directions, etc.) by focusing on the zoom action.

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 explains when to use the tool (to zoom while preserving a search query) and mentions the required condition 'Interactive Maps must be enabled'. However, it doesn't explicitly contrast with alternative zoom methods or state when not to use it, but the context is clear enough.

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