get_tiktok_ad_performance

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

No annotations are provided, so the description carries the full behavioral burden. It adds real value by naming the four video-engagement metrics and an interpretation rule, but says nothing about pagination behavior, return format, auth requirements, or rate limits for a 9-parameter list tool.

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?

Front-loads the core purpose then adds three tight metric-definition sentences. Dense and readable, though the metric list could be trimmed by an agent that already knows TikTok terminology.

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 9-parameter read tool with no annotations and no output schema, the description explains the return metrics but omits pagination limits (limit max 500 is in schema), default date behavior, and how it differs operationally from sibling performance tools. Adequate but with clear 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 100%, so all nine parameters (limit, ad_ids, statuses, client_id, date_range, etc.) are already documented in the schema. The description adds no per-parameter syntax or meaning beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource (returns TikTok Ads performance) and explicitly scopes it to the ad level with the campaign → ad group → ad hierarchy. Distinguishes it from sibling get_tiktok_campaign_performance by naming the ad grain.

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 implies performance-analysis usage and gives an interpretive heuristic (2s hold < 30% = creative-refresh signal), but never states when to use this tool versus get_tiktok_campaign_performance or get_tiktok_hourly_performance. No explicit when/when-not guidance.

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