ad_manager_fb_resume_adset

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, implying a state-changing operation. The description adds no additional behavioral context, such as what the resume process entails, potential side effects, or requirements. It simply restates the action without elaborating.

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 extremely brief (three words), which qualifies as concise but is severely under-specified. It lacks structure and fails to convey essential information. This is not effective conciseness but rather a minimal placeholder.

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?

With two parameters, a required one, and no output schema, the description is wholly inadequate. It doesn't explain what happens when resuming an ad set, any dependencies, or expected outcomes. An agent has no context to correctly execute this tool.

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%: only locationId has a description, while adsetId is left undocumented. The description does nothing to clarify adsetId's format or purpose, and it doesn't compensate for the incomplete schema. Thus, the description provides no parameter-level value beyond what the schema already offers.

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 'Resume ad set' clearly identifies the action and resource, but it adds no value beyond the tool name itself. It doesn't differentiate from siblings like ad_manager_fb_resume_ad or ad_manager_fb_resume_campaign, so an agent could easily pick the wrong one without further context.

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?

There is no guidance on when to use this tool versus the sibling resume tools. No mention of prerequisites (e.g., ad set must be paused) or conditions like integration state. An agent receives no context about the appropriate scenario.

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