google_ads_budget_create

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

Discloses mutation and reversibility via rollback_apply. No annotations provided, so description carries full burden; it covers key behavioral traits adequately but lacks details on permissions or rate limits.

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?

Four sentences, front-loaded with action and return value. No wasted words, every 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?

Covers creation purpose, parameters, typical flow, and returns id and resource_name. Could mention response format more explicitly, but given no output schema, 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?

Adds significant meaning beyond schema: explains amount is not micros, customer_id fallback, and name uniqueness. Schema coverage is 100%, but description enriches understanding greatly.

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 'Creates a new campaign budget' with specific verb and resource. It differentiates from sibling 'google_ads_budget_update' by noting that tool is for editing existing 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?

Explicitly describes the typical flow (budget.create then campaigns.create with returned budget_id) and when to use an alternative (use google_ads_budget_update for editing, not creating a second budget).

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