delete_budget

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

No annotations are provided, so the description carries full behavioral burden. 'Delete' implies destructive behavior, but nothing states whether deletion is permanent/irreversible, cascading effects on associated budget reports, or any confirmation requirements. This is a mutation tool with zero behavioral disclosure.

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 extremely short — essentially the minimum. While it is concise, the bulk is a docstring-style restatement of the parameter already in the schema. It's not wasteful, but it's under-specified rather than efficient.

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?

For a destructive operation with no annotations, no behavioral detail, and 0% schema coverage, the description should do substantially more. It lacks return-value expectations, error conditions, and side effects. Despite having an output schema, the delete tool still needs more operational 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 0%, and the description only restates 'name: Budget name' which adds minimal value over the schema's type: string. It does not explain name format, uniqueness constraints, case sensitivity, or what happens if an invalid name is given.

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 states 'Delete a budget' which is a clear verb+resource. However, it does not distinguish from siblings like delete_customer, delete_vendor, delete_invoice, etc. — though the name itself provides that differentiation. The purpose is clear but minimal.

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 vs alternatives. While delete operations are fairly self-explanatory, no context is given about prerequisites (e.g., whether a budget must not be active, whether deletion is permanent), and no mention of alternatives when a budget should be retained or archived.

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