Draft pausing an entity

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

The description transparently discloses the two-phase behavior: it only drafts and returns a preview, and actual execution requires a separate confirm_and_apply call. This goes beyond the annotations by clarifying that the operation is not immediately applied.

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 concise and well-structured, using bullet points for entity types and ID formats. Every sentence serves a purpose and there is no redundant or vague wording.

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 covers the core workflow, input format, and follow-up action, making the tool usable in context. It omits customer_id semantics, but the presence of an output schema and the clear draft/confirm flow keep it reasonably complete.

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?

The description thoroughly explains entity_type and entity_id, including the exact format for each entity type. However, customer_id is not described at all, and since the input schema has no parameter descriptions, this gap is meaningful.

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 that the tool drafts a pause action for campaigns, ad groups, ads, or keywords and returns a preview. It explicitly distinguishes the pause intent from related sibling tools like enable_entity and remove_entity.

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 description provides clear context by indicating this is a draft operation that returns a preview and instructs the caller to use confirm_and_apply with the returned plan_id to execute. It does not explicitly contrast with alternatives, but the intended workflow is well implied.

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