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

readOnlyHint=true and openWorldHint=true already declare this is a safe, external-facing read. The description only restates purpose and adds nothing about return shape, pagination, or rate limits. With annotations covering the safety profile, this is an adequate but not enriched disclosure.

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 sentence, front-loaded with the resource and the enumerated options, and it closes with the concrete usage target. Every clause earns its place with no repetition of the title or annotations.

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 read-only lister with annotations and no output schema, the description covers what the tool does and where its values go. The remaining gap is the ambiguous accountId vs adAccountId distinction and the unexplained goal parameter, which the description doesn't clarify.

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 coverage is 50%, with descriptions for platform, accountId, and profileId already present. The description adds a semantic gloss by mapping 'regions' to 'location', but it does not explain the unlabeled required adAccountId, the goal parameter, or how type/accountId interact with the profile-based parameters.

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 uses a specific verb ('List') with a specific resource ('TikTok location, language or interest options') and enumerates the exact categories: regions, languages, interests. It also names the downstream consumer (ads_create_tiktok_campaign), which sharply distinguishes it from siblings like ads_get_insights or get_tiktok_analytics.

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?

It gives clear context: these are targeting options to be passed into ads_create_tiktok_campaign targeting. This tells the agent when to call it (populating targeting values). It does not state exclusions or when-not to use, so it's clear context without full alternative routing.

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