Azure Budget 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 explicitly states that deletion is 'Permanent' and 'cannot be undone,' which accurately conveys the destructive and irreversible nature of the operation. This goes beyond a simple 'deletes' statement, providing crucial risk awareness for the agent.

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 two short sentences that immediately convey the action and the key warning. Every word is purposeful, and the most critical information ('Permanently deletes') is front-loaded. This is a model of concise writing.

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?

The description, combined with the fully detailed schema, provides adequate context for a simple delete operation. It covers the action and the irreversibility, which is the main caveat, and the parameters are well-documented in the schema. However, it does not mention potential side effects (e.g., impact on cost data) or response expectations, and there is no output schema to fill that gap.

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 already provides 100% parameter description coverage, including detailed examples and context for 'scope' and a clear definition for 'budgetName'. The tool description adds no additional parameter semantics, 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 uses a specific verb ('deletes') and resource ('cost budget'), making the action unambiguous. It clearly distinguishes this tool from sibling tools like azure_budget_list, azure_budget_get, and azure_budget_create by indicating a destructive operation.

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?

The description implies usage (when you want to remove a budget) but does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The irreversibility warning serves as a caution, but there is no explicit 'when-to-use' or 'when-not-to-use' guidance.

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