List locations

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description confirms 'Read-only.' It adds genuinely new behavioral context: 'Every plan can use every location' removes a permission/plan-gating concern the annotations do not cover, and it explains why timezone/language matter. No contradiction, though nothing is said about result size or ordering.

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?

Front-loaded with the core definition, then usage guidance, then plan availability. The browser-timezone sentence is longer than strictly necessary but does earn its place by justifying why the timezone field is returned.

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?

With no parameters and no output schema, the description carries the burden and does so: it lists the returned fields, the plan-access rule, and the downstream tools that consume this data. Nothing an agent needs to call it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description documents the shape of what is listed (country, city, location ID, timezone, language), which is helpful for interpreting results even though there are no inputs to explain.

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?

States a specific verb and resource ('List the exit locations') and enumerates the returned fields (country, city, location ID, timezone, language), which clearly separates it from siblings like list_devices. An agent knows exactly what this returns without opening any schema.

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?

Explicitly names two dependent tools (move_device, start_rotation) and the condition for calling this first ('when you're unsure what's available'), plus a second concrete scenario about matching browser timezone to exit IP. Both when-to-use and the alternative downstream tools are given.

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