get_video_info

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

No annotations exist, so the description must fully disclose behavioral traits. It does not state that the tool is read-only, nor does it mention any authentication requirements, rate limits, or side effects. The description only says 'retrieves,' implying idempotence, but lacks explicit safety or resource impact details.

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 sentence, which is concise but lacks structure. It does not highlight key information upfront or use bullet points. The brevity comes at the cost of informativeness, making it under-specified.

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 that an output schema exists (as per context signals) and only one parameter is required, the description is minimally adequate. However, it fails to specify what kind of information is retrieved, leaving ambiguity about the tool's exact output. It is complete enough for a simple tool but lacks specificity.

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 coverage is 100% (the 'url' parameter has a description). The tool description adds no further meaning beyond the schema. Consequently, the description does not compensate for any gaps, resulting in a baseline score of 3.

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 states 'Retrieves the video information,' which clearly indicates the tool fetches metadata about a YouTube video. It distinguishes from siblings like get_timed_transcript (transcripts) and get_available_languages (languages). However, the exact nature of 'video information' is not specified (e.g., title, description, statistics), making it slightly vague.

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 is provided on when to use this tool versus alternatives. For example, it does not mention that this is the go-to for basic metadata, while other siblings handle transcripts or language-specific data. The description is purely functional with no contextual advice.

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