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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that — no detail on scoping, pagination, or whether results are account-bound, which is the kind of extra context that would justify a higher score.

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 tight sentence with no filler, and the resource and purpose are front-loaded. Nothing could be removed without losing meaning.

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 values need no explanation, and annotations cover the safety profile. However, for a listing tool sitting among several near-identical audience-listing siblings, the description leaves both the platform-routing decision and the sole parameter unaddressed, leaving meaningful gaps.

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% and the single parameter advertiser_id is never mentioned in the description. An agent gets no explanation of what the parameter does, that it defaults to an empty string, or whether omitting it falls back to the connected account.

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?

Specific verb+resource: 'Lists TikTok custom + lookalike audiences', with the use case '(for ad group targeting)' clarifying intent. It does not, however, distinguish itself from sibling listing tools such as list_audiences, list_linkedin_audiences, or list_meta_audiences, so an agent must infer the platform scope from the name alone.

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 parenthetical '(for ad group targeting)' hints at context but the description never states when to call this versus the other audience-listing tools (list_audiences, list_meta_audiences, etc.) or versus create_tiktok_lookalike_audience / create_tiktok_customer_file_audience. No prerequisites, exclusions, or alternatives are given.

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