infra_billing_delete_infra_billing_record

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

With no annotations, the description carries the full burden. 'Delete' implies a destructive mutation, but the description doesn't state irreversibility, permission requirements, or side effects. It does surface the confirm parameter's behavior indirectly via the schema, and the confirm parameter description explains the preview behavior. This is minimal but not absent.

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?

Very concise: one HTTP method/path line, one purpose line, and a tags line. Front-loaded with the operation. However, the 'Tags: Infra Billing Controller' line adds no actionable information and could be considered noise.

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 tool with no annotations, no output schema, and a critical 'confirm' safety parameter with 50% schema coverage. The description provides no information about permissions, reversibility, or the confirm semantics (which are only in the schema). It is insufficient for an agent to safely invoke this deletion tool without additional context.

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 50%: the 'confirm' parameter has a detailed description in the schema (explaining the preview behavior without confirm:true). The 'uuid' parameter lacks a description in both the schema and the tool description. The description adds no parameter-level meaning beyond what the schema provides for confirm.

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+resource: 'Delete infra billing history'. Distinguishable from siblings like infra_billing_get_infra_billing_records or infra_billing_create_infra_billing_record. However, it doesn't differentiate this tool from other deletion tools in the infra billing family (delete_infra_billing_node, delte_infra_provider), leaving some ambiguity about the exact target.

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 when-to-use or when-not-to-use guidance is provided. The description doesn't mention alternatives, prerequisites, or conditions for selecting this deletion tool over others. The agent receives no guidance on when deletion is the appropriate action.

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