cloud_list_datacenters

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

No annotations present, so description carries full burden. Mentions read-only, free, and compact by default, which are useful behavioral traits. However, does not elaborate on what compact means or any other side effects. Adequate but could be more detailed.

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?

Extremely concise at three short sentences. Each sentence adds unique information: purpose, read-only/free nature, and default output format. No fluff.

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 output schema and simple operation, the description is relatively complete but lacks details on the return values (e.g., what fields are in compact vs verbose mode). Could be more comprehensive.

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 covers all 3 parameters with descriptions. The description adds value by noting 'Compact by default', clarifying the default behavior for the verbose parameter. This goes beyond the schema.

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?

Clearly states 'List datacenters', which is a specific verb and resource. The description distinguishes from sibling tools like cloud_list_locations by specifying datacenters vs locations, though the difference is not explicitly clarified. Overall strong purpose clarity.

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?

Indicates it is read-only and free, suggesting it can be used without side effects or cost. No explicit when-to-use vs alternatives, but the context implies it's a safe list operation. Adequate for a simple list tool.

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