set_location

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

With no annotations provided, the description carries the full burden. It states the action and the emulator constraint, but does not disclose prerequisites (e.g., emulator must be booted), side effects (e.g., overriding existing location), or error behavior. This is a minimal disclosure for a mutation tool.

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 a single sentence that is front-loaded with the core action and constraint. There is no redundant text or filler, making it appropriately concise.

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 simple setter with no output schema and sparse annotations, the description is insufficiently complete. It does not mention that the emulator must be running, that a serial is needed when multiple devices are connected, or what happens on failure. The agent gets little context beyond the bare 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?

Schema description coverage is only 33% (only 'serial' is described). The tool description does not elaborate on 'latitude' or 'longitude' beyond the context of setting a GPS location. It does not mention coordinate formats, ranges, or constraints, so the agent must rely on the parameter names alone.

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 uses a clear verb-resource pair ('Set the simulated GPS location') and adds a key constraint ('emulator only'), which helps distinguish it from sibling tools like set_orientation or set_appearance. It lacks an explicit sibling name but the purpose is unambiguous.

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 guidance is given on when to use this tool versus alternatives, nor any prerequisites or exclusions beyond the 'emulator only' note. The description does not mention when not to use it or how it relates to other device-control tools.

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