cortex_pipeline_resume

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

No annotations are provided, so the description carries full burden. It only states 'Resume a paused pipeline,' without disclosing side effects (e.g., state change, impact on running tasks, or error handling if pipeline is not paused). Insufficient behavioral context for an agent.

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, terse sentence with no extraneous words. It is front-loaded and efficient, appropriate for a simple tool with one parameter.

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 low complexity (1 optional parameter, no output schema), the description is minimally complete. However, it lacks details on behavior (e.g., what if pipeline is already running or not paused) and return value, making it slightly under-specified for safe autonomous invocation.

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 input schema already covers the single parameter 'pipeline_id' with default behavior. The description adds no additional meaning beyond what the schema provides, so it adds no value. Parameter semantics are adequate but not enhanced.

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 'Resume' and the resource 'paused pipeline', making the tool's purpose unambiguous. It distinguishes from sibling tools like 'pause' and 'cancel' by specifying the action on a paused state.

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 is provided on when to use this tool versus alternatives (e.g., 'cortex_pipeline_start' for starting a new pipeline, or 'cortex_pipeline_pause' for pausing). The description does not mention prerequisites (e.g., pipeline must be paused) or when not to use it.

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