youtube_get_video

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Get detailed metadata and statistics' without mentioning auth requirements, output format, rate limits, or what specific statistics are included. This is a significant transparency gap for a read operation.

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 extremely concise: one clear opening sentence followed by a single parameter explanation with an example. Every word earns its place, with no redundant 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?

For a simple single-parameter tool, the description is mostly adequate, but because there is no output schema, it should describe what 'detailed metadata and statistics' actually includes (e.g., views, likes, description). It also omits authentication context, which is important for video-specific data. This leaves some ambiguity for the agent.

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 provides only a 'Video Id' title with no description, but the tool description adds meaningful semantics: 'video_id: YouTube video ID (e.g., "dQw4w9WgXcQ")'. This gives the agent the exact format and a concrete example, fully compensating for the schema's lack of parameter detail.

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's function: 'Get detailed metadata and statistics for a specific video.' It uses a specific verb ('Get') and resource ('video'), and distinguishes from sibling tools like youtube_list_videos and youtube_search by focusing on a single known video.

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 a specific video ID but provides no explicit guidance on when to choose this over alternatives, such as youtube_analytics_video_detail or youtube_get_channel. There is no mention of exclusions or fallback tools.

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