ads_list_budgets

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the operation ('Lists campaign budgets') and does not mention pagination, default limit, response shape, or whether shared budgets are included. The description does not contradict anything, but it leaves important behavior unspecified.

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?

A single sentence with the action and resource front-loaded and no filler. Every word contributes to defining what the tool does.

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 two-parameter list operation, the description plus schema is nearly sufficient for selecting and calling the tool. However, there is no output schema and the description does not specify default limits, pagination behavior, or return value shape, leaving some gaps an agent would need to resolve.

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 description coverage is 50%, with customerId described but limit left to its min/max constraints. The description adds no parameter-level meaning, so the agent gets no help understanding how limit affects the listing or what customerId format is expected beyond the schema's one-line description.

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?

States a specific verb ('Lists'), a distinct resource ('campaign budgets'), and an account scope. This clearly distinguishes it from sibling tools such as ads_list_campaigns and ads_create_budget without needing to inspect their schemas.

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 gives no guidance on when to choose this tool over related Ads tools. It does not mention how it relates to ads_list_campaigns, ads_account_summary, or ads_create_budget, nor any prerequisites or exclusions, so the agent must infer usage from the name alone.

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