flutter_hot_restart

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does not explain side effects such as whether app state is reset, whether the operation returns a result, or what happens if the app is not running. It merely restates the operation name without adding observable behavior.

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 one short sentence with no filler and the key action is front-loaded. Every word earns its place, and it is as concise as possible for what it says.

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?

With no annotations and no output schema, the description needs to cover what happens when the tool is invoked, but it only names the action. An agent is left without knowledge of the tool's return value, side effects, or how the operation relates to flutter_hot_reload and flutter_kill, making it incomplete for a 1-parameter tool operating on a running app.

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 schema covers 100% of the single parameter and already explains that run_id comes from a previous flutter_run call. The description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 uses a specific verb ('Trigger') and names the resource ('hot restart') and scope ('running Flutter app'), making the core purpose clear. However, it does not explicitly differentiate itself from the sibling tool flutter_hot_reload, so the distinction between restart and reload is left to the tool name and prior Flutter knowledge.

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 only usage cue is that the app must be running, which is already part of the purpose. The description provides no guidance about when to prefer this tool over flutter_hot_reload, when not to use it, or what conditions must be true beyond having a run_id from a previous flutter_run call.

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