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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not state that the draft becomes live, whether the action is reversible, whether the draft is consumed, or any permission requirements. With annotations carrying the safety burden, the added context here is close to zero.

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 front-loaded sentence with no filler or repetition. It is appropriately short for its content, though brevity here stems partly from under-specification rather than disciplined editing.

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 destructive mutation tool with no output schema and two-thirds of its parameters undocumented, the definition is materially incomplete. The essential workflow facts — that a draft_id from a prepare step is required and that this commits the change — are absent, leaving the agent dependent on inference from sibling names.

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 only 33% — customer_id is documented, but draft_id and connection_context are not. The description adds no parameter meaning whatsoever; the phrase "asset-link draft" only faintly hints that draft_id identifies a previously prepared draft. It does not compensate for the coverage gap.

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 names a specific verb and resource ("confirm" + "asset-link draft"), so it is more than a bare tautology. However, it never explains what confirming actually does (applies/commits the prepared draft) and gives no differentiation from the many sibling confirm tools (asset_group_link_confirm, asset_unlink_confirm, etc.) beyond the resource word in the name.

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. Critically, the description never says a draft must first be created via the sibling google_ads_asset_link_prepare tool, nor what conditions make confirming appropriate versus abandoning the draft. The agent must infer the entire prepare/confirm workflow from naming conventions alone.

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