list_synthetics_private_locations

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

No annotations are provided, so the description carries the full burden. It states that the tool shows private location IDs, names, and tags, implying a read-only operation. However, it does not disclose any behavioral traits like auth requirements, rate limits, or whether it returns all locations.

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 two short sentences, front-loaded with the core purpose. No extraneous words; every sentence adds value.

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?

The description covers the key outputs (IDs, names, tags) and purpose. Given no output schema and no parameters, it is mostly complete. Minor improvement could mention if results are paginated or if any filtering is available.

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?

The tool has no parameters, and schema coverage is 100%. According to the rubric, baseline is 4 for zero parameters. The description adds no parameter information, but it is not needed.

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 clearly states the verb 'List' and the resource 'Synthetics private locations', specifying that it shows IDs, names, and tags. This distinguishes it from sibling tools like list_synthetics_locations and list_synthetics_global_variables.

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 mentions 'for internal testing', providing some context, but does not specify when to use this tool vs alternatives or any prerequisites. For a simple list tool with no parameters, this is adequate but lacking explicit guidance.

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