postfader_render_cancel

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

Annotations already indicate the operation is not read-only, not idempotent, and not destructive, which sets the basic safety profile. The description adds one useful behavioral note: on macOS the renderer may remain open. This is a specific caveat that helps manage expectations. However, it does not disclose other side effects, such as whether the job is marked canceled or if any cleanup occurs, leaving the agent with limited behavioral insight beyond what annotations provide.

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 that front-loads the main action and appends a platform-specific note. It is concise with no waste. However, it could be slightly clearer about the resource being canceled (render job vs monitoring), but structurally it is efficient.

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 that an output schema exists (not shown but indicated), the description does not need to explain return values. However, the description lacks clarity on what 'monitoring' refers to in the context of render jobs, and it does not mention the relationship to other postfader_render tools. The macOS caveat is useful, but overall the description leaves some ambiguity about the exact scope of the cancel operation, making it only adequately complete for an agent.

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 single parameter job_id is fully described in the schema with 'Render job ID from this MCP process.' The tool description adds no additional meaning or constraints beyond the schema. Since schema coverage is 100%, a baseline of 3 is appropriate, and the description does not need to compensate.

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 a specific verb ('Cancel') and resource ('monitoring and its owned process'), which strongly implies the intended action of canceling a render job. It distinguishes from siblings like postfader_stop_run by focusing on monitoring/process rather than runs. However, it does not explicitly say 'render job', relying on the annotation title for full clarity, which is a minor gap.

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. It does not mention that it is the cancel counterpart to postfader_render_saved_project or how it differs from postfader_stop_run. The agent is left to infer usage from the tool name and sibling list, which is insufficient.

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