ghl_ad_fb_adset_duplicate

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which is consistent. The description adds OAuth scopes and endpoint info, but does not disclose what happens to the original ad set, any limits, or that the operation creates a new ad set. Does not contradict annotations.

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 but contains redundancy ('Duplicate ad set' and 'Duplicate an existing Facebook ad set' say the same thing). Could be streamlined to one sentence and include essential details without repetition.

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 performs duplication but does not describe the return value (e.g., the new ad set ID). With no output schema, the description should indicate what the response contains. Missing this information reduces completeness.

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 one parameter (adSetId) described. The description does not add additional meaning beyond what the schema provides (e.g., format, origin of the ID). Baseline score 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?

Clearly states 'Duplicate ad set' and 'Duplicate an existing Facebook ad set', with a specific verb and resource. It is distinguishable from siblings like ghl_ad_fb_adset_delete, ghl_ad_fb_adset_upsert, and ghl_ad_fb_campaign_duplicate.

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?

No guidance on when to use this tool vs alternatives (e.g., creating a new ad set from scratch). The description lacks context for when duplication is appropriate and does not mention excluded scenarios.

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