hosting_listAvailableDatacentersV1

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

With no annotations, the description must carry the burden. It adds that the list is ordered by best match, which is useful, but does not mention read-only nature, auth requirements, or error behavior. Adequate but not fully transparent.

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 fluff, front-loaded with the main verb and resource. Every word serves a 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?

For a simple single-parameter tool without output schema, the description covers purpose, result ordering, and relationship to order. Missing details on return format (list of strings/objects) or possible errors, but overall complete.

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% with one parameter 'order_id' described as 'Order ID'. The description does not add further semantics beyond implying the order's hosting plan affects available datacenters. Baseline score applies as schema already documents the parameter.

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 hosting plans, based on order capacity, and highlights the first item as best match. This verb+resource scope distinguishes it from sibling tools like hosting_createWebsiteV1 or VPS_getDataCenterListV1.

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?

Description implies usage before setting up a hosting plan, but provides no explicit guidance on when to use vs alternatives like hosting_listOrdersV1 or VPS_getDataCenterListV1. Missing when-not-to-use or prerequisites.

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