ads_create_budget

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

No annotations are provided, so the description carries the full behavioral burden. It states only that a budget is created; it does not disclose permissions, side effects, idempotency, defaults, or what the result of the creation looks like. This is insufficient for a mutation tool with no annotation coverage.

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 concise sentence with no filler. It front-loads the primary action and adds a useful qualifier, though it is somewhat repetitive with the tool name.

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?

The tool has no output schema, no annotations, and a nested budget object, which raises the description's burden. The description is too sparse to fully guide an agent on delivery method semantics, defaults, required relationships, or expected results beyond what the schema already provides.

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?

The schema already documents customerId and amountMicros, but schema coverage is only 50%, leaving deliveryMethod and explicitlyShared unexplained. The description adds no per-parameter meaning beyond the resource concept, so it fails to compensate for the gaps in the optional nested fields.

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 descripton uses a specific verb and resource: 'Creates a campaign budget'. The added qualifier 'that can be assigned to campaigns' distinguishes it from ads_create_campaign and other ads tools.

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 implies a budgeting workflow — budgets are created so they can later be attached to campaigns — but it does not explicitly state when to choose this tool over ads_create_campaign or how it relates to ads_list_budgets. No alternatives or exclusions are named.

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