List Hosting Datacenters

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

No annotations are provided. The description adds minimal behavioral context, simply restating the action. It does not disclose response format, authorization requirements, or what 'available' means, which is a gap for a no-annotation tool.

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 a single concise sentence, front-loaded and free of unnecessary detail. It is appropriately sized for the tool's simple nature.

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 tool has no params and no output schema, but the description is still too terse. It does not specify that this lists hosting-specific datacenters, which is important given sibling tools for VPS and agency datacenters. Also, no return value details are given, leaving some ambiguity.

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 zero parameters and the schema is empty, so schema coverage is 100%. There are no parameter semantics to clarify; the description correctly implies no inputs are 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 states it 'List available datacenters,' which is a clear verb+resource. However, it does not explicitly distinguish hosting datacenters from sibling tools like vps_datacenters_list or agency_datacenters. The title and name provide the hosting context, so it is still clear enough.

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 no guidance on when to use this tool vs. alternatives. With sibling tools vps_datacenters_list and agency_datacenters, there is no differentiation or explicit context.

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