tiktok_get_audiences

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

With no annotations present, the description carries the full burden of behavioral disclosure. The verb 'List' clearly implies a read-only operation, but the description does not mention pagination, response shape, or whether the result includes all votes or is limited by the 'limit' parameter.

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?

The description is a single, front-loaded, 11-word sentence with no filler. It earns every word by stating the action, resource type, and scope efficiently.

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 list tool with only two parameters, this is minimally adequate: an agent can infer the required advertiserId and the general purpose. However, it omits usage guidance and does not clarify the semantics of the 'limit' parameter, leaving clear but non-critical 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 only 50%, and the description adds little parameter meaning beyond the schema. It does not explain that 'advertiserId' is the required account identifier beyond the obvious scope reference, and it does not clarify that 'limit' controls the number of returned audiences or pagination behavior.

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 names a specific verb ('List'), a clear resource ('custom and lookalike audiences'), and a scope ('for a TikTok advertiser account'). It clearly conveys what the tool does, though it does not explicitly differentiate itself from siblings like tiktok_get_audience_details.

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?

There is no guidance on when to use this tool versus alternatives such as tiktok_get_audience_details or tiktok_get_audience_overlap. The intended use is only implied by the phrasing 'List...', with no explicit when/when-not or alternative routing.

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