e2e_delete_node

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

No annotations are supplied, so the description carries the full burden. It does disclose the most important trait — the operation is irreversible and takes the local disk with it — which is valuable. It still omits permission requirements, whether attached volumes or data survive, and idempotency/repeat-call behavior for an irreversible mutation.

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 filler, with the destructive consequence placed immediately after the action statement. Every clause earns its place.

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 an irreversible delete with no annotations and no output schema, the description covers the safety-critical warning but not the operational context an agent needs: preconditions, interaction with attached volumes/security groups, and how to recover or verify success. Adequate but with clear gaps.

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 description coverage is 100%, so node_id, location, and project_id are already documented in the schema. The description adds no format, default, or disambiguation detail (e.g., when location/project_id are needed versus optional), so baseline 3 applies.

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?

States a specific verb pair and resource ('Terminate and delete a compute node from E2E Cloud'), which clearly separates it from e2e_create_node and e2e_list_nodes. It does not explicitly distinguish itself from the ambiguous e2e_node_action, which could plausibly also destroy a node, so it stops short of 5.

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 by the destructive warning ('permanently removes the node'), so an agent understands this is the terminal operation on a node. However, there is no explicit when-to-use/when-not guidance, no prerequisite ordering (e.g., stop node or detach volumes first), and no named alternative for lifecycle operations like stop/reboot.

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