Ytdlp Remove Chapters

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

Annotations already mark the tool as not read-only and not idempotent, so the description's mention of downloading and modifying is consistent. It adds that ffmpeg is needed, but lacks details on file creation, temporary storage, or potential side effects. With openWorldHint=true, more transparency would be helpful.

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 two sentences and front-loaded with the core action. It avoids unnecessary detail, but could be slightly more informative without losing conciseness.

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 (13 nested parameters, output schema, download+modify), the description is too brief. It fails to explain how to configure regex filters, what the output is, or the effect of dryRun. The output schema exists but is not referenced. The description leaves significant gaps for an agent to use the tool correctly.

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 has 13 complex parameters with 0% schema description coverage. The description only vaguely refers to 'configured regex filters', which maps to the 'postprocess.removeChapters' property. It does not explain required parameters like 'url' or optional ones like auth, format, dryRun, etc. This is insufficient guidance for an agent.

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 'Download' and resource 'media URL', and specifies the action 'remove chapters using regex filters'. It distinguishes from siblings like ytdlp_download_video (download only) and ytdlp_apply_sponsorblock (sponsorblock).

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 says 'Use for chapter removal workflows that need ffmpeg cuts', which implies the tool requires ffmpeg and is for custom regex filtering. It does not explicitly exclude alternatives like sponsorblock, but the sibling context provides differentiation.

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