billing_provider_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without revealing whether deletion is permanent, irreversible, whether it cascades to related entities (e.g., billing nodes, history), or if special permissions are required. For a destructive mutation tool, this is a significant gap in transparency.

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 a single short sentence with no wasted words, which is concise. However, it is so sparse that it lacks useful structure or front-loading of key behavioral caveats. It is appropriately terse for a simple operation, but it does not enrich the agent's understanding.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is incomplete. It does not cover side effects, irreversibility, idempotency, or any constraints that might influence call decisions. An agent needs more context to safely invoke a delete operation on a billing provider.

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?

The input schema documents the single 'uuid' parameter with 'Provider UUID' at 100% coverage. Since schema_description_coverage is high, the baseline is 3. The description adds no additional meaning beyond what the schema already provides, but it does not need to compensate for any missing parameter documentation.

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 clearly states a specific verb and resource: 'Delete a billing provider'. It properly identifies the operation for the billing_provider_delete tool and distinguishes it from sibling tools like billing_provider_create or billing_provider_update by its action. However, it does not elaborate on what a 'billing provider' is, which is minimal but not misleading.

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 when not to delete a billing provider or what conditions must hold. No mention of prerequisites, consequences, or the relationship to other billing operations. The name implies the purpose, but the description does not provide explicit usage context or differentiate among the many delete tools in the sibling set.

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