ghl_ad_fb_ad_pause

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

Annotations provide readOnlyHint=false and destructiveHint=false, indicating mutation. Description adds endpoint and OAuth scopes but does not disclose behavior for edge cases (e.g., pausing an already paused ad) or describe side effects beyond the API call itself.

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 short (3 lines) and includes useful endpoint and OAuth scope information without redundancy. It is front-loaded with the action and resource.

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 tool is simple, and the description covers the endpoint and OAuth scopes. However, it lacks information about expected response or error conditions (e.g., ad not found, ad already paused). Given no output schema, more context would be helpful.

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 100% with descriptions for both parameters ('Ad identifier', 'Location identifier'). The description adds no additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 title 'Pause ad' and description 'Pause a running Facebook ad' use a specific verb+resource (pause + ad) and clearly distinguish this tool from sibling tools like ghl_ad_fb_ad_resume (resume) and ghl_ad_fb_adset_pause (pause ad set).

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 the tool is for pausing a running ad but provides no explicit guidance on when to use it over alternatives, nor does it mention prerequisites (e.g., ad must be running) or exclude cases like already-paused ads.

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