Ytdlp Execute Expert

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

Beyond annotations (destructiveHint=true, readOnlyHint=false), the description discloses that the tool is disabled by default, dry-run is enabled by default, and unsafe/path-gated flags are blocked. This adds critical safety context without contradicting the annotations.

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?

Two sentences front-load the purpose and key constraints. Every sentence adds value with no redundancy or unnecessary words.

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 covers purpose, usage guidelines, and safety restrictions well. The existence of an output schema excuses the lack of return value explanation. However, given the tool's destructive nature and open-world hint, additional context on error handling or success conditions would be beneficial. Still, overall quite complete for an expert tool with multiple conditions.

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 does not explain any of the four parameters (url, args, dryRun, output). The parameter names are somewhat self-explanatory, but for a raw execution tool, the description should provide guidance on how to use args, the output object, and constraints. Without this, the agent lacks essential usage details.

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 'Execute reviewed raw yt-dlp argv' as the action, specifies the resource 'yt-dlp argv', and distinguishes from siblings by noting 'only when typed tools cannot express the request.' This provides a specific verb+resource+scope.

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?

Explicitly states when to use the tool ('only when typed tools cannot express the request'), when not to (if typed tools can handle it), and provides prerequisites ('YTDLP_MCP_ENABLE_EXPERT=true') and default behavior ('dry-run is default') along with restrictions ('unsafe/path-gated flags are blocked by policy').

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