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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds substantive context the annotations cannot: re-running a deploy or publish workflow repeats that side effect, and only finished runs are eligible. That is real consequence-level disclosure, though it doesn't say whether the call blocks until completion.

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, the action and its scope front-loaded, followed by the risk caveat. Nothing is padded and no sentence is 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?

With two fully documented params, rich annotations and no output schema, the description covers what an agent needs to invoke it. It stops short of saying what happens after the call (async vs blocking, what is returned), which is the one remaining gap.

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 100% and both parameters are documented in the schema, so the baseline applies. The description's 'by run_id from gh_actions' merely restates the schema's own 'The run's id from gh_actions' and adds no format or constraint detail beyond it.

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 (run ... again) and resource (all jobs of a finished GitHub Actions run) with the scoping qualifier 'all the jobs'. That implicitly distinguishes it from the sibling gh_actions_rerun_failed, but the sibling is never named, so an agent still has to infer the split.

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?

'by run_id from gh_actions' and 'check what the workflow does first' imply the prerequisite (obtain the run first, understand consequences), but there is no explicit when-to-use vs gh_actions_rerun_failed, gh_actions_dispatch, or gh_actions_cancel. Usage is inferable rather than stated.

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