google_ads_budget_get

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

Even though annotations are absent, the description explicitly says 'Read-only' and discloses important nuances like shared budgets and that total_budget is null unless CUSTOM_PERIOD. This fully offsets the lack of annotations.

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 two sentences but packed with value: first defines the action and lists return fields, second gives a safety warning. No fluff, front-loaded with the core purpose.

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?

With no output schema, the description fully enumerates return fields and edge cases (null total_budget, shared budgets). It also supplies the read-only safety context and a pointer to the update tool, making it self-sufficient for a get operation.

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 100%, with both parameters already explained (including customer_id fallback). The description adds no further parameter-level detail, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Fetches the campaign-budget record attached to a campaign.' It clearly distinguishes from sibling tools like google_ads_budget_update and google_ads_budget_create by focusing on retrieval.

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 provides a clear usage context by advising to check reference_count before calling google_ads_budget_update, implying this tool is for pre-update verification. It doesn't explicitly state when not to use it or name alternatives, but the context is sufficient.

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