set_geolocation

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing beyond the basic action. It does not say whether the override persists across navigations, whether it applies only to the current session, whether it needs a CDP/permission grant, or that it mutates browser state.

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?

A single short sentence that front-loads the action and is free of waste. It is arguably too terse rather than bloated, but structurally it is clean.

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 browser-state-mutating tool with no annotations, no output schema, and zero parameter documentation, the definition is under-specified. An agent cannot tell the effect scope, persistence, or how to revert it.

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% for 4 parameters, so the description must compensate and it does not. Latitude/longitude are self-evident by name, but the optional 'accuracy' parameter (meters, 0-100) and the required sessionId are never explained in prose.

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 gives a specific verb ('Set or override') and resource ('geolocation for the page'), so it is immediately clear what the tool does. It does not, however, distinguish itself from the sibling clear_geolocation or explain how it relates to set_device_metrics/emulate_network_conditions.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative clear_geolocation for undoing the override. The agent must infer all routing decisions from the name alone.

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