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

Annotations already supply readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds genuinely new context: the required 'repo' scope and write access, plus the no-op behavior when the run is not queued, which explains why the idempotent hint holds. It does not describe the return payload for the 'reported, not changed' case.

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 tight sentences, front-loaded with the action and its effect. The parenthetical issue reference is the only near-disposable element, and everything else earns its place.

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?

With no output schema, the description carries return-behavior burden and does address the failure path ('reported, not changed') plus auth requirements. It is slightly thin on how to confirm the priority was applied or check queue ordering, but nothing essential for a correct call is missing.

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 only 33% — only run_id is documented (and the description's queued-state constraint restates run semantics rather than adding parameter detail). Neither 'owner' nor 'repo' is explained in the schema or the description, so two of three parameters remain undocumented. The brief mention of 'repo' scope does not 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?

States a specific verb and resource ('Move a QUEUED workflow run into the priority lane') and immediately explains the mechanism ('the runner claims it ahead of the fair-share order across repositories'). This is easily distinguished from siblings like gluecron_cancel_workflow_run or gluecron_list_workflow_runs.

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?

Gives an explicit precondition and exclusion: 'Only queued runs; a running or finished run is reported, not changed.' The when-not case is spelled out clearly. It stops short of naming an alternative tool (e.g., how to inspect queue state), so it is strong but not exhaustive.

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