mcp_agent_restart

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the target of the restart (server process vs whole device), the hardware scope (Pi, Pico, ESP32), and that the flag is a silent no-op on Mac. It omits downtime, permission requirements, and whether the restart is graceful.

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?

Two tight sentences, zero filler, with the primary action front-loaded and the parameter caveat immediately after.

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 mutation tool with no annotations and no output schema, key facts are missing: what the call returns, how the caller knows the restart succeeded, and the format of the required `agent` identifier.

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%, so the description must compensate. It fully explains `reboot`, including the platform-dependent no-op, but says nothing about `agent` — whether it is a name, ID, or host, or how to discover valid values.

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?

States a specific verb and resource ('Restart `agent`'s server process') and immediately scopes it against the broader reboot alternative, so an agent can tell it apart from mcp_agent_upgrade and mcp_agent_logs without opening a schema.

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?

Gives clear conditional guidance for the two modes ('Pass reboot=true to reboot the whole device instead') and a platform exception (Mac ignores it). It does not, however, say when to prefer this over sibling tools like mcp_agent_upgrade.

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