Google Ad Manager MCP Server

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

No annotations are provided, so the description carries the full burden. It mentions that resuming allows ad delivery based on schedule and targeting, which adds some behavioral context, but lacks details on permissions, rate limits, or side effects like whether it affects billing or requires approval.

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 front-loaded with the core purpose, followed by brief context and structured sections for args and returns. Every sentence adds value without redundancy, making it efficient and well-organized.

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 tool's moderate complexity (a mutation action), no annotations, and an output schema present, the description covers purpose and parameters adequately. However, it could benefit from more behavioral details, such as prerequisites or error conditions, to be fully 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?

Schema description coverage is 0%, but the description compensates by explaining that 'line_item_id' is 'The line item ID to resume,' adding meaning beyond the schema's type definition. With only one parameter, this is sufficient for clarity.

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 the verb ('resume') and resource ('paused line item'), specifying that it restarts ad delivery based on schedule and targeting. It distinguishes from sibling tools like 'pause_line_item' by describing the opposite action.

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 implies usage context by stating 'previously paused line item,' indicating when to use this tool. However, it doesn't explicitly mention when not to use it or name alternatives, such as whether to use 'update_line_item_name' for other modifications.

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