Set Location

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

The description discloses that the tool overrides the real location and that clearing restores it, implying reversibility. Annotations already indicate it is not read-only and not destructive, and the description aligns with these. It does not go into side effects like whether the override persists, but the core behavior is transparent.

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, front-loaded sentence that covers both actions (override and clear) with zero wasted words. It is immediately actionable.

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 set/clear tool with no output schema, the description covers the main behaviors. It does not mention prerequisites like device allocation, but the device parameter description in the schema already points to listing available devices. Minor gaps like session scope are not critical for basic usage.

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%, with each parameter already documented (e.g., latitude says 'Omit together with longitude to clear'). The description adds the high-level pattern of setting vs clearing but does not add per-parameter semantics beyond the schema. 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?

The description states a specific action ('Override the GPS location') and the resource (device), and clearly distinguishes between setting and clearing. It is not a tautology and is unique among siblings since no other tool deals with 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 provides clear instructions on how to set (provide lat/long) and clear (omit both). It implies use cases like simulating location, though it does not explicitly mention alternatives or exclusions. Since there is no sibling location tool, this is sufficient.

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