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

No annotations are provided, so the description carries the behavioral burden. It notes the wire name is shared but rows retain TikTok-native targeting semantics, adding useful context. The verb 'List' implies read-only, and it states 'for the authenticated user', indicating auth scope. However, it does not explicitly declare non-destructive behavior, nor mention pagination or return format, leaving moderate gaps.

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?

Two concise sentences plus a required note and an example. The core purpose is front-loaded, and the extra semantics note and example are placed after. No wasted words, and the structure aids quick comprehension.

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?

For a simple zero-parameter list tool, the description covers the core purpose, the user scope, and provides an example. It does not detail the return structure or pagination, but since there is no output schema and the tool is straightforward, this is acceptable. The note about TikTok-native semantics adds depth.

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?

The input schema is empty (0 parameters), and schema description coverage is 100% trivially. The description explicitly states 'REQUIRED: none' and provides an example call, which clarifies that no arguments are needed. This adds value beyond the empty schema, aligning with the baseline for zero-parameter tools.

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?

States the exact verb 'List', the resource 'saved interest packs', and clarifies they are 'reusable audience targeting bundles'. It clearly differentiates from sibling tools like interests_get (single fetch) and interests_archive by specifying 'saved' and the listing scope.

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 makes the usage context explicit: it lists all saved interest packs for the authenticated user. While it does not name alternative tools or exclusions, the purpose is clear enough that an agent knows to use this when it wants to enumerate saved packs, not for fetching a specific one or archiving.

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