flutter_hot_reload

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

No annotations are provided, so the description carries the behavioral burden. It discloses the prerequisite, the key limitation of plain reloads, and the meaning of full_restart. It does not discuss failure modes or side effects, but it provides substantial behavioral context beyond a bare operation label.

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 compact and well-structured: a one-sentence purpose, a prerequisite, a clear usage caveat, and an args block. Every sentence earns its place, and the most important operational information is front-loaded.

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 that an output schema exists, return values do not need explanation. The description covers the prerequisite, the full_restart decision, and the boolean flag. The main gap is that package/serial semantics are delegated to 'elsewhere', and error behavior is not described, but the tool is still usable in a toolset with established conventions.

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 has 0% description coverage, so the description must compensate. It clearly explains full_restart ('hot restart instead of hot reload'), but package and serial are only described as 'as elsewhere', which relies on conventions from other tools rather than defining them here. This is useful but not self-contained.

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 ('Apply Dart source edits') and a specific resource ('the running app'), making the tool's purpose immediately clear. It distinguishes this from sibling tools like flutter_attach (connection) and flutter_diagnose (inspection) by focusing on applying source edits.

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 explicitly says 'Requires flutter_attach first', establishing the prerequisite. It also gives concrete guidance on when to use full_restart instead: after changing initState, global state, or main(), which a plain reload cannot pick up. This is strong when-vs-alternative guidance.

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