restart_stage

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

Annotations indicate non-destructive, non-idempotent, and open-world. Description adds that it restarts a specific stage, but does not disclose side effects like dependencies re-running or downstream stages affected. With annotations covering basic traits, description provides minimal extra value.

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?

Single sentence with no redundancy. Front-loaded with action and context. Could be slightly more detailed about restrictions but is 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?

With no output schema, description doesn't explain return value or confirmation. For a mutation tool, missing behavioral details (e.g., success indicator). Overall adequate but could be more complete given lack of output schema.

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?

Both parameters have descriptions in input schema (100% coverage). Description adds no additional meaning beyond 'execution ID' and 'stage ID'. Baseline 3 is appropriate as schema already documents parameters.

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?

Uses specific verb 'restart' and describes resource ('stage within a pipeline execution'). Sibling tools like 'pause_execution' and 'resume_execution' suggest finer granularity, but description doesn't differentiate from 'trigger_pipeline' or 'cancel_execution'. Clear but lacks sibling distinction.

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?

No guidance on when to use this tool versus alternatives like 'trigger_pipeline' or 'resume_execution'. Does not mention prerequisites (e.g., stage must be stopped or failed). Implied usage but no explicit context.

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