restart_instance

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

No annotations are provided, so the description must disclose behavioral traits. It explains the default name selection and the all_instances flag, but does not mention potential side effects like service interruption or state consistency during restart.

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?

The description is extremely concise: two sentences plus a brief arg list. It front-loads the core action and efficiently explains parameters without unnecessary text.

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?

For a simple tool like restart, the description covers essential behavior: the action, default behavior for name, and the all_instances option. An output schema exists (as per context), so return values are not required in the description. Slight lacking detail on error cases or prerequisites, but overall adequate.

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 0%, meaning no parameter descriptions in the schema. The description adds meaning by explaining that 'name' defaults to 'primary' when omitted and all_instances is False, and that setting all_instances to True restarts all instances, compensating well for the lack of schema documentation.

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 verb 'Restart' and the resource 'Multipass instances'. It distinguishes from sibling tools like stop_instance, start_instance, and suspend_instance by specifying a restart action.

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 explains default behavior for the 'name' parameter (defaults to 'primary' when omitted and all_instances is False) and the effect of 'all_instances'. It provides context on when to use the tool, though it does not explicitly mention when not to use it.

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