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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the write-but-not-destructive profile is covered structurally. The description adds a genuinely useful detail the annotations don't carry: the pack lives in the caller's private AdsAgent workspace rather than being written back to Meta. It stops short of stating overwrite behavior when interest_pack_name collides with an existing pack.

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?

A single well-formed sentence with the read step and the save step front-loaded and no filler. It's tight, though it spends its limited budget on prose framing rather than the parameter detail an agent actually needs.

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 output schema covers return values, so that burden is lifted. Against a 5-parameter, 0%-coverage schema with no annotations on auth scope, though, the description leaves meaningful gaps: what tags/notes do, what happens on duplicate pack names, and whether the pack is created or appended to.

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% across 5 parameters, so the description must compensate and largely does not. It hints at ad_account_id and adset_id ('one Ad Set in your authorized Meta accounts') and at interest_pack_name ('reusable audience pack'), but leaves tags and notes completely undefined, and doesn't clarify whether ad_account_id is required to scope adset_id resolution.

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?

Specific verb pair (read targeting, save a reusable audience pack) plus concrete resources (one Ad Set, private AdsAgent workspace). An agent can distinguish it as the fetch-and-persist composite from siblings like interests_fetch_from_adset and interests_save_targets, though those siblings are never named.

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 scenario (capture an Ad Set's targeting as a reusable pack), but never states when to use this rather than interests_fetch_from_adset (read-only) or interests_save_targets (save manual targets). The agent must infer the distinction from sibling names alone.

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