google_ads_budget_get

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

Discloses read-only nature, lists all return fields, and explains the shared budget implication with reference_count. With no annotations, full burden is on description, which handles it well.

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?

Two compact sentences: first states purpose and output fields, second provides behavioral hint linking to update tool. No redundancy, ideally front-loaded.

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 output schema, description enumerates return fields. Parameter behaviors are explained. Could mention error handling, but overall adequate for a get tool with simple inputs.

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%, so baseline is 3. Description adds value by explaining that mureo resolves budget_id internally for campaign_id and that customer_id defaults to env vars, exceeding the schema 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?

The description clearly states it fetches the campaign-budget record for a campaign and lists the returned fields. It distinguishes from sibling tools like google_ads_budget_update by advising to check reference_count before updating.

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?

Declares the tool is read-only and provides explicit guidance to check reference_count before calling the update sibling. Lacks explicit when-not-to-use, but context is clear.

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