bare_metal_delete_bare_metal_server

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

No annotations are provided, so the description carries the disclosure burden. It discloses the destructive action and the 'smart identifier resolution' behavior, which is useful. However, it does not state irreversibility, prerequisites, or what happens to associated resources, leaving some behavioral gaps for a deletion operation.

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 with the main action, followed by a useful identifier-resolution note and a clear Args/Returns structure. It is slightly padded by the return line, but overall efficient.

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 single-parameter delete tool with an output schema present, the description covers the core action and parameter semantics. It lacks notes on error behavior or destructive consequences, but given the tool's simplicity, it is sufficiently complete for an agent to invoke it correctly.

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 0%, so the description must compensate. It does so well by explaining that server_identifier accepts a label, hostname, or UUID, adding meaningful information beyond the bare 'type: string' in 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?

The description clearly states the action ('Delete a bare metal server') with a specific verb and resource. It doesn't explicitly differentiate from sibling tools, but the name and scope are unambiguous, so an agent can identify what this tool does.

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?

Usage is implied: use this tool when you want to delete a bare metal server. There are no explicit when-to-use vs. alternative statements, exclusions, or prerequisites, but the operation is self-contained and there is no competing bare-metal delete sibling.

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