get_video

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

With no annotations, the description carries the full burden for behavioral disclosure, but it only lists return content and does not mention auth requirements, side effects, error behavior, or explicitly confirm read-only semantics. The 'Get' verb implies read-only, but the description does not elaborate on any behavioral traits.

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 main description is concise and front-loaded with a clear sentence. The redundant 'Args' block adds little value beyond the schema, but it is brief and does not hinder readability.

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 description provides key information about the return content (full details, slideshow images, TikTok publish status) for a simple single-parameter read tool. However, without an output schema or mention of permissions/limitations, it is not exhaustive but adequate for the tool's simplicity.

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 description restates the parameter name and adds minimal context ('The video ID.') without explaining format, source, or semantics. Since schema description coverage is 0%, the description should compensate but does not add much beyond the schema property title.

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 a specific verb ('Get') and resource ('full details for a single video'), and highlights key included content (slideshow images and TikTok publish status). This distinguishes it from sibling tools like list_videos or get_video_analytics.

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 implies usage for retrieving details of a single video, but offers no explicit guidance on when to use it versus alternatives or any exclusions. It does not mention sibling tools or specific scenarios.

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