dashboard_restart

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

No annotations are provided, so the description carries full burden. It does not disclose potential side effects (e.g., disruption to active sessions), required permissions, or whether the restart is safe. The phrase 'restart' implies disruption but no details are given.

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 redundant words. Front-loaded with the action and resource, concise and complete.

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 restart tool with no parameters and no output schema, the description is adequate but could mention prerequisites (e.g., required dashboard state) or confirmation of success beyond URL/port.

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?

With zero parameters, the description correctly focuses on the action and outcome. It adds meaning beyond the empty schema by specifying what the tool does and returns.

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 action (restart), the resource (follow-along dashboard), and the output (URL and port). It distinguishes from sibling tools like dashboard_info which likely provides information without restarting.

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 implies when to use (when you need to restart the dashboard) but does not explicitly state when not to use or mention alternatives like dashboard_info for non-restart needs.

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