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

No annotations are provided, so the description carries full burden of behavioral disclosure. It states the intended effect (restores real GPS fix) but doesn't describe what happens if no simulated location was set, whether this affects other apps or sessions, any permissions needed, or what the success/error behavior looks like. Minimal behavioral context beyond the core action.

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?

Two sentences, zero waste. States the purpose and provides a useful counterpart reference. Perfectly concise and front-loaded.

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-parameter tool with a clear inverse relationship, the description covers the core purpose well. However, given there are no annotations and no output schema, it could add value by describing edge cases (e.g., calling when no location was simulated) or confirming it's a safe non-destructive operation. Adequate but not rich.

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 100% (udid documented as 'iOS device UDID'), so the schema carries the parameter load. The description adds nothing about the udid parameter but also doesn't need to given full coverage. Baseline 3 is appropriate.

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?

Clear verb+resource (clears simulated GPS location) with a clear statement of effect (device returns to real CoreLocation fix). Names its counterpart ios_set_location for context. Does not explicitly distinguish from device_clear_location sibling, but the iOS-specific scope is evident from the name and mention of CoreLocation.

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 counterpart reference suggests it pairs with ios_set_location but does not explicitly state when to use this vs alternatives like device_clear_location. No explicit when/when-not guidance, but the context of being the inverse of ios_set_location is implied. No exclusions or alternative tool names mentioned beyond the counterpart.

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