ghl_ad_fb_ad_resume

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

The description includes the HTTP endpoint (POST) and OAuth scopes (adPublishing.write), which adds behavioral context beyond the annotations. Annotations already indicate non-read-only and non-destructive, so the description adds value with specific auth and method details.

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 with minimal extra lines, though it includes technical metadata (endpoint version, source) that may not be essential for an agent. Still, it is front-loaded and non-redundant.

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 action and endpoint but lacks any mention of return value or success indication. Since there is no output schema, the description could provide more context about the outcome.

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 all parameters described in the input schema. The description adds no additional parameter explanations, so baseline score of 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 description clearly states 'Resume a paused Facebook ad', which specifies the verb (resume) and the resource (paused Facebook ad). Among siblings, there is a distinct 'pause' tool, so it is well-differentiated.

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 for resuming paused ads but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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