delete_budgets

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

With no annotations, the description conveys the destructive nature implicitly through 'delete' but doesn't disclose permanence, permissions, or the interaction between budget_ids and other filters. It does add the AND-combination rule, which is useful but basic.

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?

Two short sentences deliver the core action and necessary constraints, with no redundant words or repetition of schema details.

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 tool has 7 parameters but full schema coverage and an output schema reduce the need for description. The description provides essential guardrails for safe deletion, though it could mention irreversibility or error behavior for missing filters.

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 coverage is 100%, so all parameters are already described. The description adds meaningful cross-parameter behavior: 'at least one filter' and 'AND' combination, which go beyond the individual schema descriptions.

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 and resource, 'Delete budgets', and clarifies the filter-based targeting. It clearly distinguishes the tool from siblings like delete_expenses and update_budgets.

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 states when to use the tool by requiring at least one filter and explains that all filters are combined with AND. It doesn't explicitly mention alternatives but the context is clear.

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