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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond them — no statement about how archived packs are treated by default, how pagination terminates, or what 'saved' scope excludes, which are the useful behavioral details an agent would need.

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?

One short sentence with no waste, but it is under-specified rather than concise — brevity here costs information an agent needs. Nothing is front-loaded because there is nothing else to front-load.

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?

An output schema exists, so return-value explanation is not required. Still, for a paginated, filterable list tool with four undocumented parameters and a dense sibling namespace, the description is far too thin to make the call unambiguous.

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%: limit, cursor, search, and include_archived are documented only by type/min/max/default, and the description supplies no meaning for any of them. It doesn't say that limit bounds page size, that cursor is a continuation token, or what search matches against — a clear miss where the description was obliged to compensate.

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 gives a verb and resource ('List saved audience packs'), so the basic operation is inferable. However, it never differentiates from close siblings like interests_search, interests_get, interests_fetch_from_adset, or interests_archive, and the 'audience packs' phrasing is not obviously the same thing as the 'interests' namespace the tool lives in.

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 about when to call this versus interests_search or interests_get, nor any mention of pagination workflow or archived inclusion. The agent is left to infer all routing decisions from the tool name alone.

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