rerun_action_run

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

Discloses constraints (only on completed runs, active runs error), behavioral effects (creates new run, increments run_attempt, original unchanged), and version requirement (Gitea 1.26.0+). No annotations exist, so description carries full burden and performs well.

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?

Four sentences, no filler, front-loaded with main action, then constraints, then prerequisites, then alternative. Very 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?

Covers purpose, usage, constraints, and alternative well. Lacks information about return value (e.g., does it return the new run ID?), but given no output schema, the description is still fairly complete. Minor 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 description does not add new parameter semantics beyond mentioning runId in context. Baseline 3 is appropriate.

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?

Description clearly states the tool reruns an entire Actions workflow run by runId, and distinguishes itself from the sibling tool rerun_action_run_failed_jobs.

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?

Explicitly instructs to call get_action_run first to confirm run completion and to confirm runId with the user. Also advises when to use rerun_action_run_failed_jobs instead.

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