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 of behavioral disclosure. It fails to mention any behavioral traits such as authentication requirements (access_token parameter is undocumented), rate limits, error conditions, or what happens if the video is not 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 a single, concise sentence with no wasted words. However, it is perhaps too terse given the lack of other documentation; it could benefit from slightly more detail without becoming verbose.

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?

The tool is simple, but without annotations or output schema, the description is insufficient. It does not specify what 'details' includes, nor does it explain the access_token parameter. The agent needs more context to use the tool 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 description coverage is 50% (only video_id has a description). The description does not add any meaning beyond the schema for video_id, and it completely ignores access_token, which lacks a description in the schema as well. This leaves a crucial parameter undefined.

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 action (get details), resource (TikTok video), and identifier (by ID). It distinguishes from sibling tools like list_tiktok_videos which lists multiple videos, and get_tiktok_user which is a different resource.

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?

No guidance on when to use this tool versus alternatives such as search or list tools. There is no mention of prerequisites or when not to use it. The description relies on the name and schema to imply usage, but fails to provide explicit context.

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