analyze_videos

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

No annotations are provided, so the description must disclose behavioral traits. It only states what is collected, but fails to mention read-only nature, authentication needs, rate limits, or behavior on private/missing videos. The description is too brief for a tool with 11 parameters.

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 that front-loads the purpose. However, it is too minimal for the tool's complexity and does not include additional structured information that would aid an agent.

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 complexity (11 parameters, no annotations, no schema descriptions), the description is severely lacking. It does not hint at the output format or behavior, and fails to help an agent decide when to use this tool over siblings like get_transcript or get_video_comments.

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 0%, and the description adds no information about any of the 11 parameters. Parameters like 'comment_order', 'force_refresh', and 'min_comment_length' are not explained, leaving the agent without necessary semantic context.

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 verb 'collect' and the resource 'specific videos', listing the data types collected (transcripts, metadata, optional comments). It is specific and implies a combined functionality, though it does not explicitly differentiate from sibling tools like get_transcript or get_video_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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or contexts where other tools like search_videos or get_transcript would be more appropriate.

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