ad_manager_google_delete_ad_account

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

The description only states 'Delete ad account' and adds no behavioral context beyond what annotations already provide. Annotations declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, but the description does not elaborate on the irreversibility, consequences, or the permanence of the deletion. For a destructive operation, the agent would benefit from a warning about the impact, which is absent.

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, short sentence: 'Delete ad account' – extremely concise and front-loaded. There is no wasted wording. It is appropriately minimal for a clear action, though it lacks explanatory detail that could be added without bloat.

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 description is inadequate for a destructive operation with no output schema. It fails to specify which ad platform (Google) explicitly, and it does not mention potential side effects, whether the deletion is permanent, or any required permissions or prerequisites. Given the existence of multiple platform-specific delete_ad_account tools, the missing platform context is a notable omission.

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?

All parameters (locationId and adAccountId) are fully documented in the schema with descriptions, so the description adds nothing extra. The schema coverage is 100%, so the baseline is 3. The description does not provide additional meaning or context for the parameters; it simply restates the tool's action.

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 the action (delete) and resource (ad account), making the core purpose unambiguous. However, it does not explicitly mention that this is specific to Google Ads, relying on the tool name 'ad_manager_google_delete_ad_account' for platform differentiation. With sibling tools for Facebook and LinkedIn also named 'delete_ad_account', the description alone does not disambiguate them, though it is still clear on what the tool does.

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 guidance on when to use this tool versus the Facebook or LinkedIn delete_ad_account alternatives. No prerequisites, conditions, or context are given. An agent would have to infer from the tool name which platform it targets, and there is no advice on when deletion is appropriate or what to check beforehand. This is a significant gap given multiple similar siblings.

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