billing_node_delete

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond the word 'Delete' — no indication of irreversibility, whether associated billing history or node records are cascaded, or what authorization is required. For a destructive mutation, this is a meaningful gap even with the lower bar set by annotations.

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?

It is a single front-loaded fragment with no filler, which is good, but it is under-specified rather than genuinely concise. There is no room wasted, yet no useful structure or detail is provided either.

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 destructive, one-parameter tool with no output schema and no annotation detail beyond hints, the description should carry more weight — consequences, scope of deletion, and parameter meaning. It leaves all of that unaddressed.

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 0%, and the description never references the single required parameter. The agent must infer that 'uuid' identifies the billing node to delete purely from the schema's type and format, with no confirmation of whether it is the node UUID or a billing-record UUID.

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?

It names a specific verb (Delete) and resource (infra billing node), so the basic operation is identifiable. However, it does not differentiate from adjacent siblings such as nodes_delete, billing_history_delete, or billing_node_update, and the term 'infra billing node' is not clarified anywhere. An agent cannot tell from the text alone whether this targets a Remnawave node record or a billing-specific entity.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. With siblings like billing_history_delete and nodes_delete in the list, the description should explain which entity this removes versus those, but it offers nothing.

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