Restart an overseer task

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

Beyond the destructiveHint annotation, the description discloses important behaviors: automatic stop-before-restart, ambiguous-name error listing candidates, and refusal of user-started running tasks unless force is set. This significantly enriches the agent's understanding of side effects and restrictions.

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?

Three concise sentences, each carrying essential information without redundancy. Front-loaded with the primary action and followed by necessary caveats and error behavior.

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?

The description is complete for a restart operation: it covers input selection, error conditions, and safety restrictions. No output schema is present, but return values are not critical for this destructive action, and the description provides enough context for correct invocation.

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?

Despite zero schema description coverage, the description explains both parameters: task can be a numeric id or name substring, and force overrides the refusal of running user-started tasks. This fully compensates for the schema's lack of descriptive text.

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 clearly states the tool restarts a task by id or name substring, using a specific verb and resource. It distinguishes itself from sibling tools like overseer_stop by explicitly noting it stops the task first if running.

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?

The description gives practical usage guidance: use a numeric id when a name matches multiple tasks, and set force to override refusal of user-started running tasks. It does not explicitly contrast with alternatives but provides clear contextual usage rules.

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