get_tiktok_video

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

No annotations are provided, so the description carries the full burden. It describes the return format (JSON with specific fields) but does not disclose behavioral traits such as authentication requirements, rate limits, error handling, or whether the request is destructive. The description adds some value but lacks transparency on these important aspects.

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 very concise, consisting of two short sentences. The first sentence front-loads the core purpose and output format. Every word adds value, with no redundancy or 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 the tool's simplicity (single required parameter, no output schema, no nested objects), the description is largely complete. It provides enough detail for an AI agent to use it correctly. However, it could mention potential error cases (e.g., invalid ID) or rate limits, but these are not critical for a basic retrieval tool.

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 covers the single parameter with a description explaining to extract the video ID from a URL. The tool description reinforces this by mentioning 'URL or ID'. Since schema coverage is 100%, the description provides additional context on how to derive the ID, going beyond the schema's basic definition.

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 clearly states the tool retrieves detailed info for a single TikTok video by ID as JSON. It lists the specific data returned (caption, author, music, stats, URLs, etc.), distinguishing it from sibling tools that handle other entities like hashtags, profiles, or comments.

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 the tool: 'Use when the user has a specific TikTok video URL or ID.' This provides clear context. However, it does not mention when not to use it or suggest alternative tools for searches or multiple videos, which are available as siblings.

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