get_tiktok_auction_rankings

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

With no annotations, the description carries full burden and does well: it discloses the sort order (worst offenders to top), a computed field (below_average_count), the impression filter and its default, and null-handling for tiers lacking video_quality_score. It omits auth requirements, pagination, and response envelope shape, keeping it short of a 5.

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?

Three dense but well-packed sentences, front-loaded with the returned fields before behavior. Every sentence carries information, though the phrase about the platform burning creatives is slightly editorial.

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?

With no output schema and no annotations, the description adequately specifies the return fields, their value domains, the derived count, and sorting. It stops short of describing the overall result envelope or how multiple filter parameters combine, but covers what an agent needs to invoke it correctly.

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 coverage is 100%, so the schema already documents all seven parameters and their defaults. The description only elaborates on min_impressions (its throttle purpose) and says nothing about ad_ids, campaign_ids, advertiser_ids, or the date range filters, so it adds little beyond 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?

States a specific verb (Returns) and resource (per-ad TikTok ranking signals) and enumerates the exact output fields: video_quality_score, engagement_rate_ranking, conversion_rate_ranking. An agent can distinguish this from get_tiktok_ad_performance and get_meta_auction_rankings purely from the description.

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?

Usage is implied through the statement that '1+ below-average rankings is a creative-refresh trigger on TikTok,' which signals the intended scenario. However, it never explicitly says when to choose this over siblings like get_tiktok_ad_performance or get_tiktok_campaign_performance, so the guidance remains inferential.

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