List Locations

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the description only needs to add extra context. It adds that the tool returns all locations and describes the output fields, but does not disclose additional behavioral aspects like pagination or data freshness. This is moderate value beyond the annotations, so a 3 is appropriate.

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 concise and well-structured: a brief opening statement, a bullet list of the output fields, and a one-sentence use case. Every sentence contributes meaning, with no redundancy or filler, making it efficient and easy to parse.

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 list operation with no required parameters and no output schema, the description is complete: it defines the tool's scope, lists the returned fields, and gives a clear use case. The annotations cover safety, and the schema covers the only param, so nothing critical 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?

The input schema covers the single parameter 'response_format' with a clear enum and description, achieving 100% schema coverage. The description does not mention parameters, but the schema fully documents them, so the baseline of 3 applies; no additional value is added, but none is necessary.

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 tool lists available datacenter locations, uses a specific verb ('List') and resource ('datacenter locations'), and distinguishes it from sibling list tools by focusing on locations. It also provides useful details about the returned fields (code, city, country, network zone), making the purpose unmistakable.

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 context for when to use this tool ('Use this to choose where to deploy your server'). It does not explicitly name alternatives or explain when not to use it, but the context is sufficient for typical selection among sibling list tools, earning a 4.

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