list_locations

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

No annotations are provided, so the description carries full burden. 'List all locations' implies a read-only operation but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, or what 'all' means (e.g., all accessible locations vs. all in system). For a tool with zero annotation coverage, this is insufficient.

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 extremely concise with just three words, front-loaded with the core action. There's zero waste or unnecessary elaboration, making it easy to parse while still conveying the basic purpose.

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?

Given no annotations, no output schema, and a simple 0-parameter tool, the description is incomplete. It doesn't explain what 'locations' are, what data is returned, or how this differs from other list tools. For adequate context, it should clarify the resource type and typical use cases.

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 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of parameters. The description doesn't need to add parameter information, and 'List all locations' appropriately implies no filtering parameters are needed. Baseline for 0 parameters is 4.

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 'List all locations' clearly states the verb ('List') and resource ('locations'), but it's vague about scope and doesn't distinguish from sibling tools like 'list_datacenters' or 'list_servers'. It provides basic purpose but lacks specificity about what 'locations' means in this context.

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?

No guidance is provided about when to use this tool versus alternatives. With many sibling list tools (e.g., list_datacenters, list_servers, list_networks), the description doesn't explain what makes 'locations' different or when it should be preferred over other listing tools.

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