tiktok get audience details

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description reinforces read-only status and adds a mild availability qualifier about DMP endpoints, but does not disclose deeper behaviors like pagination, result shape, or endpoint-specific limitations. No contradiction exists.

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 short and front-loaded with the core action and resource. The phrase 'Read-only only' is somewhat redundant given the annotations, but it does not bloat the description materially.

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 tool with a complete input schema and an output schema, the core information is present. However, the description lacks guidance on how this tool relates to tiktok_get_audiences and leaves the 'DMP endpoints accessible' condition ambiguous, so completeness is adequate but not strong.

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 parameters are already documented in the schema. The description itself adds little about how limit, audienceIds, advertiserId, or includeSavedAudiences behave beyond what the schema provides, earning the baseline.

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 a read-only GET operation on audience details and specifies the audience types: custom/lookalike/saved. This helps distinguish it from report-oriented tools, though it does not explicitly name sibling tools like tiktok_get_audiences.

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 only usage hint is 'where TikTok DMP endpoints are accessible,' which is vague and does not explain when to choose this tool over tiktok_get_audiences or tiktok_get_audience_report. No explicit when-to-use or when-not-to-use guidance is provided.

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