makemkv_job_status

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

Annotations provide readOnlyHint=true and idempotentHint=true, indicating safe, repeatable reads. The description adds context about checking 'status and progress,' which suggests it returns dynamic job information, but doesn't detail rate limits, auth needs, or specific behavioral traits like error handling. No contradiction with annotations exists.

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 ('Check the status and progress') without unnecessary words. Every part earns its place by directly conveying the tool's function.

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), annotations covering safety, and an output schema (which handles return values), the description is reasonably complete. It could improve by mentioning the job ID parameter or error cases, but it adequately supports agent usage in this context.

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?

With 0% schema description coverage (parameter 'job_id' has minimal description), the description compensates by implying the parameter's purpose ('rip job'), but doesn't specify format or constraints. Since there's only one parameter, the baseline is high, and the description adds some meaning beyond the schema, though not exhaustively.

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 ('Check') and resource ('status and progress of a rip job'), making the purpose evident. It distinguishes from siblings like 'makemkv_list_jobs' (which lists jobs) and 'makemkv_cancel_job' (which cancels jobs) by focusing on status/progress of a specific job. However, it doesn't explicitly mention the job ID parameter, which could enhance specificity.

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 when needing to check a rip job's status, but doesn't explicitly state when to use this vs. alternatives like 'makemkv_list_jobs' (for listing all jobs) or 'makemkv_monitor' (which might monitor ongoing jobs). No exclusions or prerequisites are mentioned, leaving some ambiguity in context.

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