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

The readOnlyHint annotation already indicates a non-destructive operation, and the description's 'preview' is consistent with that. However, the description adds no further insight into side effects, return format, or whether it modifies state beyond the annotation.

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 a single concise sentence with no unnecessary words. It conveys the core action and target concisely, though a bit more detail could improve clarity without harming brevity.

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 lacks context about what a 'reusable audience pack' is, what 'preview' returns, or how the output relates to other interest tools. Given the minimal schema (no parameter docs) and no output schema shown, the description is insufficient for an agent to fully understand the tool's behavior.

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% (no parameter descriptions), and the tool description does not explain the purpose or expected format of the ad_account_id or adset_id parameters. This leaves the agent without any semantic guidance for the inputs.

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 states a specific verb ('preview') and resource ('reusable audience pack') tied to a single live Meta ad set, which distinguishes it from related tools like interests_list or interests_save_fetched_pack. However, 'preview' is slightly vague about whether it fetches data or shows a summary.

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 explicit guidance is provided on when to use this tool versus alternatives such as interests_get, interests_list, or interests_save_fetched_pack. The description implies a specific scope (one live ad set) but does not state conditions or contrast with sibling tools.

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