tiktok_get_audience_details

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

Since no annotations are provided, the description carries the full behavioral burden. 'Read-only only' is a genuine safety disclosure that tells the agent this call does not mutate state, and 'where TikTok DMP endpoints are accessible' hints at an availability constraint. However, it does not explain failure modes, what happens when endpoints are inaccessible, pagination, or rate-limit behavior.

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?

Two short sentences with the verb+resource front-loaded and no filler. 'Read-only only' is slightly redundant with 'Get' but functions as deliberate safety emphasis; the 'where TikTok DMP endpoints are accessible' clause is vague but costs little.

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?

No output schema exists, so the description should convey return shape, but it does not. It also fails to route among audience-related siblings and never explains what 'DMP endpoints accessible' means or how an agent should respond when the condition does not hold. For a tool with no annotations and 27 siblings, this is incomplete.

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 75%, so the schema already documents advertiserId, audienceIds, and includeSavedAudiences. The description reinforces the audience-type scope, which maps to audienceIds and includeSavedAudiences, but it adds nothing about the undocumented 'limit' parameter, including its pagination semantics.

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 states a specific verb ('Get') and resource ('custom/lookalike/saved audience details'), clearly identifying what the tool fetches and scoping it to three audience types. It does not explicitly differentiate from siblings like tiktok_get_audiences or tiktok_get_audience_overlap, and the 'where TikTok DMP endpoints are accessible' qualifier adds a scope caveat without clarifying it.

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?

No guidance on when to choose this tool over the 27 siblings, including the closely related tiktok_get_audiences, tiktok_get_audience_overlap, and tiktok_get_targeting_catalog. The DMP-accessibility caveat implies availability limits but offers no decision rule, prerequisites, or alternative routing.

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