ad_group_search_match_preview

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds that this is a preview of a state change, but says nothing about whether the preview must be applied via a separate step, how long it is valid, or that it hits the live Apple Ads API (openWorldHint).

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; the action and target are the first things read.

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 annotations cover the safety profile. Still, for a 4-required-parameter mutation-preview with half the schema undocumented, the description leaves the preview-to-apply lifecycle and any placement-type constraints (Search Results only) unaddressed.

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 only 50%: adGroupId and enabled are undocumented in the schema. The description compensates by making 'enabling or disabling' the meaning of the enabled flag and by binding the operation to a specific ad group, so the agent can map the required inputs without guessing.

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 (preview enabling/disabling) and a specific resource (Apple Search Match on a Search Results ad group), which clearly separates it from the many pause/resume/bid preview siblings. It stops short of naming a concrete alternative or follow-up tool, so an agent must infer the surrounding workflow.

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?

The word 'Preview' implies a dry-run before applying, but the description never says when to prefer this over e.g. ad_group_update_preview or how the preview is committed (operations_apply). Usage is only implied, not stated.

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