billing_provider_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so irreversibility is largely covered by structured data. The description adds nothing beyond the identifier — it does not say whether the delete is permanent, what happens to billing nodes/history referencing the provider, or whether the call fails if dependencies exist.

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?

A single front-loaded sentence with no filler. It is terse to the point of under-specification, but nothing in it is wasted.

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?

This is a destructive mutation with no output schema and no annotations beyond the destructive flag, so the description should carry the burden of dependency/irreversibility context. It delivers none, leaving an agent unable to predict side effects on related billing resources.

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?

With only one parameter and 0% schema description coverage, the phrase 'by uuid' is the sole signal, and it does tell the agent the identifier is a UUID rather than a name or numeric id. Beyond that it adds no format, validation, or sourcing guidance, so it sits at the baseline.

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 (Delete) and resource (infra provider, identified by uuid), which is enough for an agent to distinguish it from the get/create/update/list siblings. It does not explicitly name those alternatives, and the term 'infra provider' sits slightly at odds with the 'billing_provider_*' namespace, but the intent is unambiguous.

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?

No statement of when to use this versus billing_provider_update (e.g., deactivate vs. remove) or billing_providers_list, and no prerequisites such as whether dependent billing nodes must be cleared first. Usage is only implied by the verb.

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