resume_authoring_run

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

No annotations are provided, so the description carries the burden. The description says 'resume' which implies the run was paused/suspended, but it doesn't specify side effects, state requirements, or error conditions. It is adequate but not detailed.

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 sentence, front-loaded with the verb. It is concise and contains no filler.

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?

The tool has only one parameter and an output schema (not shown). Given low complexity, the description is minimally adequate but lacks context about return value, state transitions, or error handling.

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 coverage is 0% (no descriptions in schema). The description does not explain the 'run_id' parameter beyond its title. With only one parameter, a brief hint would help but the title is self-explanatory.

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 states 'Resume a previous authoring run by id.' It uses a specific verb ('Resume') and resource ('authoring run'), and the sibling tools include 'start_authoring_run' and 'list_authoring_runs', which are clearly related. However, it does not explicitly differentiate from 'reopen_authoring_stage' or 'confirm_authoring_stage'.

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?

No guidance on when to use this tool vs. alternatives like 'start_authoring_run' or 'reopen_authoring_stage'. It does not mention prerequisites (e.g., run must exist, must be in a resumable state).

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