billing_node_delete

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

With no annotations provided, the description must carry the full behavioral burden. It conveys that the operation is destructive, but it does not disclose whether deletion is permanent, whether it cascades to related billing records, or whether any confirmation is needed. This is a significant transparency gap for a delete 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 extremely concise with no filler words, and the core action is front-loaded. However, the brevity comes at the cost of omitting important behavioral context, so it is efficient but not fully informative.

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?

Although the tool has only one required parameter and no output schema, it is a destructive operation with no annotations. The description lacks any mention of permanence, related side effects, or conditions for safe usage, leaving the agent under-informed for a potentially impactful call.

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%; the single uuid parameter is already described as 'Billing node UUID'. The description adds no additional meaning beyond the schema, so the baseline score of 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?

The description states a specific verb ('Delete') and a specific resource ('a billing node'), which clearly identifies the operation. It is distinct from related siblings like billing_node_create and billing_node_update, though it does not explicitly distinguish itself from nodes_delete beyond the 'billing' qualifier.

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 guidance on when to use this tool versus alternatives such as billing_node_update or nodes_delete, and no mention of prerequisites or side effects. The agent must infer usage solely from the tool name and resource type.

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