hosting_listAvailableDatacentersV1

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

Without annotations, the description adds that the list is ordered by best match based on capacity and plan, giving insight into prioritization. It does not mention any side effects, but as a read operation, this is sufficient.

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?

Two sentences, no wasted words. The first defines the primary action, the second adds crucial ordering information. Efficiently communicates key details.

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 read tool with one parameter and no output schema, the description covers purpose, filtering criteria, and ordering. It lacks detail on return structure but is adequate for the task.

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% for the single parameter 'order_id', so baseline is 3. The description adds no extra semantics beyond what the schema provides ('Order ID').

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 retrieves a list of datacenters for setting up hosting plans, based on order-specific capacity and plan. There is no sibling tool with identical purpose, and the verb 'Retrieve' indicates a read operation.

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 implies usage after obtaining an order ID and during hosting plan setup, providing clear context. However, it does not explicitly state when not to use or compare to alternatives, though no direct alternative exists.

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