makemkv_rip_title

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

With no annotations, the description carries full burden but only mentions that it 'Returns immediately with a job ID'. It doesn't disclose behavioral traits like whether it's destructive (likely writes files), requires specific permissions, has rate limits, or what the job ID is used for (e.g., monitoring with 'makemkv_job_status'). This leaves significant gaps for a mutation tool.

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, efficient sentence that front-loads the core action and key behavioral note (immediate return with job ID). There is no wasted verbiage, making it highly concise and well-structured.

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 a mutation tool with no annotations, 0% schema coverage, and an output schema (which might describe the job ID), the description is incomplete. It lacks details on parameters, behavioral implications (e.g., file system changes), and integration with sibling tools like 'makemkv_job_status', making it inadequate for safe and effective use.

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%, so the description must compensate but adds no parameter information. It doesn't explain what 'title_index' or 'drive_index' mean, what 'output_dir' defaults to, or how to determine valid values. This fails to address the undocumented parameters, leaving semantics unclear.

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 action ('Start ripping') and resource ('a single title from disc'), distinguishing it from sibling tools like 'makemkv_rip_all' which rips all titles. However, it doesn't specify what 'ripping' entails (e.g., extracting video content), leaving some ambiguity.

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 implies usage for single-title ripping versus 'makemkv_rip_all' for all titles, but lacks explicit guidance on prerequisites (e.g., disc must be scanned first) or when to use alternatives like 'makemkv_backup_disc'. It provides basic context but no exclusions or detailed comparisons.

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