cassette_job_status

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

Despite no annotations, the description discloses key behaviors: it is a single-call operation (not a loop) and wait_for_change_sec allows up to 30 seconds for job progression. No contradictions or missing critical traits.

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 consists of two concise sentences, each adding essential information. No wasted words; front-loaded with purpose and usage.

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?

While the description covers the main use case, it omits explanations for three of four parameters (limit, job_id, session_id), which are important for correct invocation. Given the presence of an output schema, this is a moderate gap.

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%, but the description only explains wait_for_change_sec. Parameters limit, job_id, and session_id are not mentioned, leaving their roles unclear (e.g., pagination or filtering).

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 tool's purpose: 'Re-attach to a job whose cassette_run_job call did not return'. This specific verb-resource combination distinguishes it from siblings like cassette_run_job (which starts a job) and cassette_cancel_job (which cancels).

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 explicitly states when to use (when cassette_run_job did not return due to host restart, cancellation, or wait=false) and provides guidance: 'Call it once and act on the phase; it is not a progress loop.' It also explains the wait_for_change_sec parameter's role.

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