google_ads_budget_create

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

No annotations provided, but description fully discloses that it's mutating, not automatically reversible, and suggests recording before-state with mureo_state_action_log_append for rollback. Also states budget period is immutable after creation.

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?

Single paragraph but well-structured with logical flow: purpose, return, mutation warning, typical flow, alternative, immutability. Could be slightly more concise but each sentence adds value.

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 no annotations or output schema, description covers all needed: purpose, return, side effects, rollback suggestion, workflow, parameter relationships, and immutability constraints. 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?

Schema coverage is 100%, but description adds context: clarifies amount is not micros with examples, explains mutually exclusive total_amount and total_amount_micros, and relates period to total amounts. Adds practical usage context beyond 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?

Description clearly states it creates a new campaign budget, returns id and resource_name, and distinguishes from sibling google_ads_budget_update. Also provides typical flow (budget.create followed by campaigns.create).

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?

Explicitly says when to use this tool (creating budgets) and when not (editing existing budgets, use update instead). Provides typical flow and notes that budget type is fixed at creation.

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