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 the user-scoping constraint and the note that 'rows retain TikTok-native targeting semantics', which is genuinely useful context, but says nothing about result size, ordering, or pagination.

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?

Front-loaded with purpose, followed by scoping, then REQUIRED and an EXAMPLE; little waste. The 'wire name is shared, but rows retain TikTok-native targeting semantics' sentence is slightly opaque but short.

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 read-only list tool whose annotations already cover safety, this is nearly adequate, but with no output schema the description should hint at what a returned pack looks like, and the undocumented connection_context parameter leaves a gap an agent must guess at.

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%, so the description must carry the load for the single parameter, connection_context. It only asserts 'REQUIRED: none', which is helpful for required-ness but leaves the one parameter's meaning and expected mctx_v1 format entirely unexplained in both schema and description.

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 a specific verb (list) and resource (saved interest packs) and even glosses the resource as 'reusable audience targeting bundles', which an agent can act on. It does not, however, distinguish itself from siblings like interests_get or interests_fetch_from_adset, so the scope is clear but the differentiation is not.

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 scopes usage to 'the authenticated user' and states 'REQUIRED: none' plus a call example, which implies it is the entry-point listing call. But it never says when to prefer this over interests_get or interests_fetch_from_adset, so alternatives are left to inference.

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