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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds a useful non-obvious side effect—'pushed source is retained'—but it does not explain permissions, job state after cancellation, or whether the operation is idempotent.

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 front-loaded sentence with no wasted words, which is structurally efficient. However, it is too sparse for the complexity of a cancellation operation with two required parameters.

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?

For a mutation tool with no output schema and 0% parameter description coverage, the description leaves out critical information: what exactly is canceled, what workspace/job_id refer to, and what happens to the job's state. The retention note helps but is insufficient.

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%, and both required parameters (workspace and job_id) are completely undocumented in the description. The only contextual phrase, 'pushed source,' does not clarify either parameter, so the description fails to compensate for the schema gap.

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 says 'Cancel operation,' which is a vague resource label rather than clearly stating it cancels a job. It does not distinguish this tool from siblings like publish_cancel or agent_runs_cancel, though the name and annotation title make the intent inferable.

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?

There is no guidance on when to use this versus jobs_get, publish_cancel, agent_runs_cancel, or other cancellation tools. It also omits prerequisites such as whether the job must be in a running state before cancellation.

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