google_ads_budget_update

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

In the absence of annotations, the description covers key behaviors: it's mutating, reversible, returns the updated budget, and shares effects. Missing details like rate limits or auth, but adequate for this simple mutation.

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?

Three concise sentences with no redundant information. The primary action is stated first, followed by key behavioral notes. Perfectly front-loaded.

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 simple update tool with three parameters and no output schema, the description provides all necessary context: mutation, rollback, shared budget implication, and parameter clarification. No gaps.

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?

Although schema covers 100% of parameters, the description adds valuable context: clarifies that 'amount' is in currency units (not micros) and that 'budget_id' comes from google_ads_budget_get. This goes beyond the schema.

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 'Sets the daily amount on an existing campaign budget,' which is a specific verb-resource combination. It distinguishes from sibling tools like google_ads_budget_create (new budget) and google_ads_budget_get (read-only).

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: reversible via rollback_apply, shared budget warning with a recommended check. Lacks explicit 'when not to use' or alternatives, but the shared budget caution effectively guides appropriate usage.

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