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

There are no annotations, so the description carries the full burden. It does not disclose whether this operation is read-only or mutating, what side effects (if any) it has, or what permissions are required. The word 'prepare' suggests no direct mutation, but this is not stated, making it ambiguous.

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 one short sentence, but it is under-specified rather than concise. It provides no actionable detail, so it does not earn its place; it reads more like a placeholder than a helpful definition.

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?

Given the lack of annotations, no output schema, and one undocumented parameter, the description is far from complete. It does not explain the purpose of the 'prepare' step, the expected return, or how it fits into the recommendation workflow, leaving the agent with insufficient information.

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 50%: customer_id has a description, but recommendation_resource_name does not, and the tool description adds no parameter-level detail. It fails to explain what recommendation_resource_name is, how to obtain it, or its format, leaving a significant gap for the agent.

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 clear verb-resource pair: 'Prepare applying' one recommendation, which distinguishes it from the confirm step (apply_confirm) and other recommendation actions like dismiss. It is unambiguous about the resource type, though it doesn't clarify what 'prepare' entails operationally.

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?

No guidance is given on when to use this tool versus the confirm step or the dismiss variants. It does not mention that it should be called before google_ads_recommendation_apply_confirm or that it is for previewing or dry-running, leaving the agent to infer the workflow.

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