clear_geolocation

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether this reverts to real geolocation, whether it requires an active emulation, whether it is idempotent, or what the response is — all material for a mutation-style operation.

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?

Extremely short and front-loaded with no filler, which is structurally fine for a simple operation. But at four words it is under-specified rather than genuinely concise — brevity here reflects missing information, not efficiency.

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 tool with no annotations, no output schema, and an undocumented required parameter, the description should at minimum name the sessionId requirement and the reverting effect. Neither is present, so an agent lacks what it needs to call this confidently.

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?

There is one required parameter (sessionId) with 0% schema description coverage, and the description does not mention it at all. Since the schema supplies only a type/format pattern and no prose, the description fails to compensate for the coverage gap on the required parameter.

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 verb+resource pair ('clear' + 'geolocation override') tells an agent roughly what happens and implicitly distinguishes it from the sibling set_geolocation. However, it never states what is being cleared (the emulated override vs. the session's real geolocation), so the boundary with siblings like reset_network_conditions is left to inference.

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?

No when-to-use guidance, no prerequisites, and no reference to the natural alternative (set_geolocation) or related reset tools. An agent must guess the context in which clearing is appropriate.

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