tiktok get audiences

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and side-effect profile. The description adds no further behavioral context (e.g., pagination behavior, rate limits, or response format). Given the annotations, this is adequate but not enriched beyond the structured data.

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, front-loaded sentence that directly states the function and scope. No wasted words, and the essential information is presented immediately.

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?

The tool is simple with only three parameters and no nested objects. An output schema exists, so return structure is covered. The description, combined with the schema and annotations, provides sufficient context for an agent to invoke the tool correctly. Minor gaps like pagination usage are already in the schema.

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 100%, so all three parameters (advertiserId, page, limit) are fully documented in the schema. The description does not add any parameter-specific nuance beyond what the schema already provides. With high schema coverage, the baseline of 3 is appropriate.

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 clearly states the action (list) and the resource (custom and lookalike audiences) for a specific account. It distinguishes from siblings like tiktok_get_audience_details (which implies details for a single audience) and tiktok_get_audience_report (which implies reporting). The scope is unambiguous and the tool's function is immediately evident.

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 conveys what the tool does but does not explicitly state when to use it versus alternatives such as tiktok_get_audience_details or tiktok_get_audience_overlap. No explicit exclusions or alternative routing is provided; the usage context is implied by the sibling names rather than stated.

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