list_synthetics_locations

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

No annotations provided. Description honestly presents a read-only list operation with no destructive actions. Lacks details on pagination or rate limits, but for a parameterless list, these are likely minimal.

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 concise sentences stating purpose and usage context. No redundant information.

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 parameterless list with no output schema, the description provides all necessary context: what it lists, types of locations, and when to use it.

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?

No parameters in the input schema. Description adds no parameter info, but baseline is 4 for zero-parameter tools as per guidelines.

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?

Description clearly states it lists Synthetics testing locations, both managed and private. Differentiates from sibling list_synthetics_private_locations by explicitly including both types.

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?

States 'Useful for configuring where synthetic tests run,' providing clear context for when to use. No explicit when-not-to-use, but the purpose is sufficiently clear for a straightforward list tool.

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