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

With no annotations provided, the description carries the behavioral disclosure burden. It goes beyond the name by explaining that the helper service stops pushing mocked fixes and that apps fall back to the real GPS/network provider. It does not cover edge cases like no-op behavior when mocking is already off, but this is meaningful transparency for a simple stop 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?

The description is two sentences with no filler. The first sentence delivers the core definition, and the second adds useful pairing and behavioral context. It is front-loaded and every clause contributes.

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 one-required-parameter tool with no output schema, the description gives enough to invoke it correctly: what it does, on which platform, and what effect it has. It omits only minor details like idempotence or what happens if no mock is active, which are not critical for this tool's simplicity.

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 input schema already documents the only parameter, udid, as 'Device serial number (UDID)', giving 100% schema description coverage. The description adds no parameter-specific detail, but the high coverage means this is acceptable under the baseline.

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 names a specific verb ('Stop'), a specific resource ('mock GPS'), and the platform ('Android device'), so an agent immediately knows what the tool does. It also explicitly identifies itself as the counterpart to device_set_location, distinguishing it from the setter and from sibling tools like ios_clear_location.

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 gives clear context: use this tool when you want to stop mocked GPS and return to real GPS/network provider, and it explicitly frames the tool as the counterpart to device_set_location. It does not enumerate exclusions such as iOS or edge cases when no mock is active, but the Android qualifier and counterpart framing provide sufficient guidance.

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