set_budget

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

Annotations indicate destructive hint and not read-only. Description adds that it is financial, requires confirmation, and defaults to dry-run, which mitigates destructiveness. This adds valuable behavioral context beyond annotations alone.

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 concise sentences: first states purpose, second provides usage rule. No unnecessary words; efficient and easy to parse.

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?

Given three parameters and no output schema, the description covers the main behavioral aspects: financial nature, dry-run default, and confirmation requirement. Lacks information on return values or error states, but is sufficient for a straightforward set operation.

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 has no descriptions (0% coverage). Description explains that 'target_budget' is the desired value and 'confirm' controls execution. However, 'ad_id' is not explained, and units for 'target_budget' are missing. Partially compensates but leaves gaps.

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 clearly states the tool sets a target budget and computes the delta from current. It distinguishes from sibling 'increase_budget' by specifying a fixed target rather than an incremental change. However, 'computing delta' could be interpreted ambiguously.

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?

Provides explicit guidance that confirm=True is required for execution and default is dry-run. This helps the agent know when to actually apply changes. Could be improved by mentioning alternatives like 'increase_budget' or 'get_account_budget' for different needs.

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