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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds a genuinely useful behavioral detail — that an empty name is rejected with {'error': 'invalid_name'} — which is not derivable from the schema. However it says nothing about what a rename affects, whether it can be reverted, or any permission requirements, so it adds only partial value on top of the 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?

Two short sentences with the main action front-loaded and zero filler. The inline error-object snippet is slightly awkward formatting and the mixed German/English reduces scannability marginally.

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?

An output schema exists so return values need not be described, and the empty-name validation plus workspace semantics are covered. For a destructive-flagged mutation with three parameters, it should still clarify prerequisites (e.g., that campaign_id must belong to the specified workspace) and whether the rename is reversible.

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 0%, so the description must carry the parameter burden; it explains only 'workspace' (optional when there is just one workspace). 'campaign_id' and 'new_name' are not documented in the description, but their meaning is fairly self-evident from the tool name, so partial compensation is acceptable.

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 states a specific verb+resource in 'Kampagnen-Name ändern', making it clearly distinct from siblings like ads_update_campaign_status, ads_update_campaign_budget, or ads_update_campaign_settings. It is slightly weakened by being a terse German sentence in an otherwise English toolset, and by not explicitly stating that it targets Google Ads campaigns only.

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?

There is no when-to-use guidance and no mention of the closest alternative (ads_update_campaign_settings), which could plausibly also rename a campaign. The only contextual hint is the workspace note about single-workspace accounts.

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