search_tiktok_ads

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context beyond those annotations: exact case-sensitive matching, the public nature of the Ad Library, and that spend/impressions are returned as bands, not exact figures. No contradiction with annotations.

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 three sentences, each earning its place: purpose, usage modes with an example, and return values plus required companion tools. It is front-loaded and contains no filler.

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?

Given no output schema, the description explicitly lists return fields (ad ids, run dates, spend/impression bands, media URLs) and directs to analyze tools for visual analysis. It could mention pagination behavior via cursor/limit, but the description is otherwise complete for a search tool with good annotations.

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?

The schema has 0% description coverage, so the description must compensate. It provides critical semantics for the primary parameter 'query', explaining it can be an exact advertiser name or a keyword, and highlights case sensitivity. However, it doesn't explain 'limit' or 'cursor', but these are standard pagination parameters and the query guidance is the key missing piece.

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 and resource: 'Search TikTok's public Ad Library for the ads an advertiser is running.' It also lists the return fields (ad ids, run dates, spend/impression bands, media URLs), distinguishing it from siblings like analyze_ad_video and analyze_ad_image.

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?

Explicitly instructs to use the exact registered advertiser name (case-sensitive) or a keyword, and names appropriate alternatives: 'For complete analysis ... you MUST also use analyze_ad_video (passing ad_id) or analyze_ad_image.' This gives clear context for when to use this tool versus others, though it doesn't explicitly state when not to use it.

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