tiktok get audience overlap

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Read-only' agrees with that. The description adds modest context about the diagnostic scope, but no additional behavioral traits such as rate limits, auth requirements, or how the overlap is computed. With annotations covering the safety profile, 3 is appropriate.

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 one focused sentence that front-loads the core purpose and scope. There is no filler, no redundant restatement of the schema, and no wasted words.

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 diagnostic tool, the one-line description plus rich annotations, a detailed schema, and an output schema is almost complete. It loses one point because it doesn't clarify the relationship between the compared entities or suggest the intended use case, leaving some agent reasoning to inference.

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 the baseline is 3 even without parameter details in the description. The entity list loosely maps to parameters like adgroupIds, includeSavedAudiences, and smartPlus, but it does not add meaning beyond the schema. The schema itself documents defaults, bounds, and smart_plus 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 states a specific diagnostic resource — audience overlap — and names the entity types it spans: ad groups, custom audiences, saved audiences, and targeting fields. It clearly differentiates from sibling tools like tiktok_get_audience_details and tiktok_get_audience_report by focusing on overlap rather than details or reports.

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 gives no guidance about when to choose this tool over sibling audience tools or how it relates to tiktok_get_audiences, tiktok_get_audience_details, tiktok_get_audience_report, or tiktok_get_targeting. There is no when-to-use or when-not-to-use signal; the agent must infer suitability from the name and scope alone.

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