increase_budget

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

Description adds key behavioral details beyond annotations: 'Financial — requires confirm=True to execute; default is dry-run.' This informs the AI about the execution mode and financial consequence, complementing the destructiveHint and readOnlyHint annotations without contradiction.

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, well-structured sentence that front-loads the purpose ('Add TON to ad budget (delta)') and adds essential context without any fluff. Every word contributes to 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?

For a 3-parameter tool with no output schema, the description covers the core behavior, financial implication, and execution mode. It lacks detail on return values or error conditions, but given the simplicity, it is fairly complete.

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?

With 0% schema description coverage, the description partially compensates by explaining that 'amount' is the delta and 'confirm' controls execution. However, 'ad_id' is not described, leaving its meaning implicit. Overall, adds some value but not fully comprehensive.

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 begins with 'Add TON to ad budget (delta)', clearly stating the specific action (add) and resource (TON to ad budget). It distinguishes from sibling tools like 'set_budget' which implies absolute budget setting, and includes additional context about financial nature and execution mode.

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 indicates this tool is for delta additions, contrasting with set_budget for absolute values. It mentions the confirm parameter for execution vs dry-run. While not explicitly stating when not to use it, the context and sibling list provide sufficient guidance.

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