cloud_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. It states the tool is read-only and free, which is helpful, but it fails to disclose key behaviors like pagination, data freshness, or what 'compact' vs 'verbose' outputs differ. The description does not contradict annotations as there are none.

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 only three fragments. Every word serves a purpose. However, it lacks structure and could benefit from a full sentence or bullet points. Overall, conciseness is good, but structure is minimal.

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 the absence of an output schema and the presence of nested objects in parameters, the description should elaborate on what 'locations' entails, the effect of parameters, and output format. It fails to provide sufficient context for an agent to invoke the tool correctly.

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?

Schema coverage is 100%, so the schema already describes each parameter. The description adds the context 'Compact by default' which relates to the 'verbose' parameter, adding slight value beyond the schema. However, it does not explain the semantics of 'id' or 'query' further.

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 'List locations', identifying the verb ('List') and the resource ('locations'). It is specific enough to distinguish from sibling list tools targeting different resources. However, it could be more precise about what 'locations' refer to (e.g., datacenters, availability zones).

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 includes 'Read only, free' which implies safe usage without cost, but it provides no explicit guidance on when to use this tool versus alternatives like 'cloud_list_datacenters'. No mention of prerequisite context or exclusion criteria.

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