makemkv_eject

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('eject disc') but lacks details on permissions, side effects (e.g., if the drive becomes unavailable after ejection), or error conditions. This is a significant gap for a tool that performs a physical operation.

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, direct sentence with zero waste—it states the action and the parameter context efficiently. It's front-loaded and appropriately sized for a simple tool, earning full marks for 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 low complexity (one parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and a physical operation involved, it should ideally include more behavioral context (e.g., safety warnings or prerequisites) to be fully complete.

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 description adds meaning by specifying that the parameter is for 'the specified drive', which clarifies the purpose of the 'drive_index' parameter. With 0% schema description coverage and only one parameter, this compensation is effective, though it doesn't detail format or constraints beyond what's implied.

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 ('eject') and resource ('disc from the specified drive'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'makemkv_cancel_job' or 'makemkv_list_drives', which might also involve drive operations, so it doesn't reach the highest score.

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. For example, it doesn't mention prerequisites like needing a disc to be present or when to use it in relation to sibling tools such as 'makemkv_rip_all' or 'makemkv_scan_disc'. This leaves the agent with insufficient context for optimal tool selection.

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