get_tiktok_ad_details

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is clear. The description adds behavioral context by promising a 'fresh playable video URL' and detailing what information the response contains (creative, landing page, country targeting, engagement metrics). No contradictions found.

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 two concise sentences: the first states the function and the returned data categories, the second provides usage context. There is no redundant wording or unnecessary detail, making it highly efficient.

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 simple one-parameter read-only lookup, the description adequately sets expectations by listing the output content categories and linking to the appropriate sibling search tool. No output schema exists, but the enumerated detail fields are sufficient for an agent to understand what the tool provides.

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 input schema has zero description coverage for the single parameter ad_id, so the description must compensate. It does so by explaining the provenance ('from search_tiktok_ads') and the purpose (identifying a specific TikTok ad), which gives the agent enough context to provide a valid value.

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 uses a specific verb ('Get detailed information') and identifies the exact resource ('a specific TikTok ad'), while enumerating concrete data categories (full creative, landing page, country targeting, engagement metrics, playable video URL). It clearly distinguishes itself from the sibling search_tiktok_ads by specifying that it operates on an ad_id rather than performing a search.

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 explicitly states when to use this tool: 'Use this with an ad_id from search_tiktok_ads' and calls it 'Essential for analyzing ad content and extracting media URLs for visual analysis.' It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to select it appropriately.

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