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

Annotations declare destructiveHint=true and idempotentHint=false, but the description adds valuable context beyond them: it is a partial read-modify-write (only passed fields change, others are read from the live ad and written back), and it runs validation limits before the call. It does not fully spell out what specifically gets overwritten or permission requirements, keeping it at 4.

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?

Densely front-loaded: purpose, then partial-update semantics, then platform limits, then the confirm workflow. Every sentence carries information and nothing is redundant.

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 explained, and the description adequately covers mutation behavior plus the preview/apply gate for a 10-param tool. The main gap is that only three of the ten parameters receive semantic detail, leaving some room for a fully complete picture.

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?

With 0% schema description coverage, the description must compensate, and it does add real meaning for the key params: headlines (3-15, ≤30 chars), descriptions (2-4, ≤90 chars), and confirm (preview vs apply). However, path1, path2, final_url, customer_id, account_id, ad_group_id, and ad_id go unaddressed across 10 total params, so it only partially compensates.

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?

States a specific verb (EDITS) and resource (Microsoft/Bing Responsive Search Ad copy), and names the exact operation target (headline/description swap). It also implicitly distinguishes itself from a delete-and-recreate approach by contrasting with a rebuild, so an agent can identify it without opening the schema.

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?

Gives clear usage context: swap weak copy without deleting/rebuilding because a rebuild resets performance history, and explains the confirm=false preview vs confirm=true apply workflow. It stops short of naming explicit sibling alternatives (e.g. update_rsa or create_microsoft_responsive_search_ad), so it earns 4 rather than 5.

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