flutter_hot_reload

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only names the operation without explaining side effects such as whether app state is preserved, whether the app must be in debug mode, or what happens if the run_id is invalid.

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; the objective is stated immediately. It earns every word.

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 single-parameter, simple trigger tool, the description plus schema covers the basics. Still, with no annotations and no output schema, it leaves open what result to expect and does not distinguish hot reload from hot_restart, which are meaningful gaps.

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 input schema already fully documents run_id with 100% coverage, including its origin in a previous flutter_run call. The description adds no extra parameter semantics, so the baseline of 3 applies.

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 action ('Trigger a hot reload') on a specific target ('a running Flutter app'), so an agent can tell what the tool does. It does not explicitly contrast itself with the sibling flutter_hot_restart, so sibling differentiation is left to the tool names.

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 phrase 'on a running Flutter app' implies the tool should be used after a flutter_run session is active, and the run_id param reinforces this. However, there is no explicit guidance about when to choose hot reload over the sibling flutter_hot_restart or 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.