bare_metal_list_bare_metal_servers

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

The description states a return behavior ('List of bare metal servers with details') and the verb 'List' implies a read-only operation. With no annotations provided, it adds little beyond this: no mention of pagination, authorization, or side-effect guarantees, but for a zero-parameter list tool the burden is modest.

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 compact and front-loaded. The first sentence states the action and scope; the second adds return-shape detail. There is no filler, and the structure is easily scannable.

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 zero-parameter listing operation with an output schema, 'List all bare metal servers' plus the return note is essentially complete. The only missing context is explicit guidance on sibling filter/list tools, which is already penalized in usage guidelines.

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 takes no parameters, so the schema fully defines the input surface and the description needs no parameter explanation. Per the scoring convention for zero-parameter tools, this is a strong baseline.

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 uses a specific verb and resource: 'List all bare metal servers.' The 'all' makes scope explicit, but it does not explicitly distinguish this from sibling tools like bare_metal_list_bare_metal_servers_by_status or bare_metal_list_bare_metal_servers_by_region; the distinction is left to the name.

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 word 'all' implies this is the unfiltered list variant, giving a minimal usage context. However, it does not name alternatives such as the by-status or by-region list tools, nor does it state when to prefer those over this one.

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