scrape_video

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

No annotations provided, so description must disclose behavioral traits. It only states what it does (extract, build skill) without mentioning side effects, auth requirements, rate limits, or parameter interaction. For a 16-parameter tool with no schema descriptions, this is insufficient.

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?

Single sentence that front-loads the core action. Lacks bullet points or structured sections, but avoids verbosity. Could better organize the 'build Claude skill' addition.

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 16 parameters, 0 required, 0% schema descriptions, and no annotations, the description is critically incomplete. It does not cover return values (output schema exists but not referenced), parameter combinations, or tool behavior beyond basic extraction.

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 description adds minimal meaning beyond parameter names. It mentions video sources (YouTube, Vimeo, local files) which maps to url/video_file, but does not explain other 14 parameters (e.g., visual, languages, whisper_model).

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?

Description specifies verb 'Extract' and resource 'transcripts and metadata from videos' with concrete sources (YouTube, Vimeo, local files). It uniquely adds 'build Claude skill', differentiating it from sibling scrape tools that target other sources.

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 vs alternatives like scrape_docs or scrape_generic. No prerequisites or exclusions mentioned, despite many sibling tools.

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