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

Annotations already indicate destructiveHint: true and readOnlyHint: false. The description adds the scope requirement as behavioral context beyond annotations. It does not detail side effects, but given annotation coverage, the added value is significant.

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?

Two sentences: first clearly states the tool's purpose, second adds a critical requirement. No redundancy or filler. Highly 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?

The tool is simple (3 required params, no output schema), but the description lacks details on the cancellation effect (e.g., whether it's reversible, what happens to associated logs). It meets minimal needs but could be more helpful with behavior details.

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 the description does not elaborate on any of the three parameters (owner, repo, run_id). The mention of 'repo' scope is a permission requirement, not parameter documentation. This leaves the agent with no guidance on parameter meanings.

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 action ('Cancel') and the resource ('a queued/running workflow run'), distinguishing it from sibling tools like gluecron_trigger_workflow and gluecron_get_workflow_run.

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?

It mentions a prerequisite ('Requires 'repo' scope') but does not provide explicit when-to-use, when-not-to-use, or alternatives. The scope requirement offers some guidance but leaves usage context incomplete.

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