pilot_hot_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 says 'hot restart' which conveys it's faster than a full restart, but doesn't disclose whether the current app state is preserved, whether it interrupts in-flight operations, how long it takes, or what happens on failure. Given zero annotation coverage, this is a significant gap for a state-affecting operation.

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 concise sentence, no waste, adequately front-loaded. Very efficient. Could add a bit more behavioral context without hurting score, but as written it's appropriately short.

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?

Given it's a state-mutating tool with no annotations and no output schema, the description is underspecified. It doesn't explain what state is preserved, when it's appropriate (e.g., after code changes vs. to recover from a crashed state), or the return/result expectation. Sibling tools list (start_app, stop_app, tap, etc.) implies a UI testing framework, but the description doesn't connect hot restart to that workflow.

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?

The tool has 0 parameters with 100% schema coverage (empty schema means nothing to document). Baseline for 0 parameters is 4. The description correctly implies no inputs are needed, so the schema and description are consistent.

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 states a specific verb+resource: 'Performs a hot restart of the currently running app session started by this server.' It's clear this restarts the app session. However, it doesn't distinguish from sibling tools like stop_app+start_app or suggest when hot restart differs from a cold restart; siblings include start_app, stop_app, simulate_background but no other restart tool, so differentiation is limited.

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 hot restart versus stopping and starting the app, or whether it applies only to a session started by this specific server. The phrase 'started by this server' implies a constraint but doesn't explain the implications (e.g., won't work on externally-launched apps). No exclusions or alternatives mentioned.

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