Manage Workflows

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely carried by structured data. The description could have added real value by disambiguating which of the six actions are destructive (cancel_run, trigger_dispatch) versus read-only (list_workflows, get_run) — a tool-wide destructiveHint is potentially misleading without that breakdown. No mention of auth/permission requirements or rate limits.

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, zero waste, operation list front-loaded ahead of the control-field instruction. Nothing redundant.

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?

No output schema exists, so the description should have said something about what each action returns (workflow list vs run object vs log text) — an agent cannot infer the response shape for six distinct operations. Eleven parameters across a conditional action dispatch also merit a sentence on combinations, though the schema covers those requirements.

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 100% and per-parameter text already specifies which action each param applies to (e.g. runId for get_run/get_run_logs/cancel_run, ref for trigger_dispatch). The description adds nothing beyond pointing at the `action` enum, so the baseline 3 applies.

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 names a specific resource (GitHub Actions Workflows) and enumerates all six supported operations: list, trigger dispatch, inspect run status/logs, list runs, cancel. An agent can tell exactly what the tool covers, though it does not contrast itself against any sibling (none of the siblings are workflow-related, so differentiation is implicit).

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?

'Use the `action` field to select the operation' is a routing hint, not usage guidance. It never says when to prefer this tool over, say, manage_prs checks or direct API calls, nor does it explain prerequisites (auth scopes, which actions mutate state). Adequate but with clear gaps.

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