billing_node_create

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

Annotations declare readOnlyHint=false and destructiveHint=false, which tells the agent this is a non-destructive write. Beyond that the description adds nothing: it does not say whether the referenced provider/node must pre-exist, whether the call is idempotent, what happens on duplicate nodes, or what a successful creation returns.

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 phrase is four words with no structure to speak of. It is not verbose, but as with a bare one-word description, the problem is under-specification rather than conciseness — for a four-required-parameter mutation tool this is far too terse to front-load anything useful.

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?

A four-parameter, all-required mutation tool with 25% schema coverage and no output schema needs the description to explain the relationship between provider, node, and billing schedule. The description supplies none of that, leaving the agent to infer the entire semantics of the operation.

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 only 25% (only nextBillingAt is documented), so the description carries the burden for providerUuid, nodeUuid, and name — and it says nothing about them. It does not explain that providerUuid/nodeUuid are references to existing billing providers and nodes, nor what the nextBillingAt timestamp drives.

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 names a verb (Create) and a resource (billing node), so the basic operation is inferable. However, "infra billing node" is vague domain jargon, and nothing distinguishes this from siblings like billing_nodes_list, billing_node_update, billing_node_delete, or billing_provider_create — the agent must guess whether 'infra billing node' means a billing-enabled node, a provider association, or something else.

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 indication of when to use this tool versus the many adjacent billing and node tools (billing_nodes_list, billing_node_update, billing_provider_create, nodes_create). No prerequisites, no exclusions, no alternatives are mentioned.

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