Flutter Hot Reload [Pro]

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

The description explains that hot reload preserves app state (variables, navigation, scroll positions) and is faster than a full restart. However, it does not mention limitations like unsupported code changes (e.g., static fields) or potential side effects. No annotations are provided, but the description adds value beyond the name.

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 three sentences, each adding value: purpose, state preservation advantage, and prerequisite. No wasted words.

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 the tool's simplicity (no params, no output schema), the description covers essential aspects: what it does, its key benefit, and a prerequisite. It could mention unsupported code changes for completeness, but overall sufficient.

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 no parameters (schema coverage 100%), so the description's role is minimal. It adds no param info, but there are no params to describe. Baseline for 0 params is 4, and the description does not contradict this.

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 clearly states the tool triggers a hot reload on a connected Flutter app. It specifies the verb 'trigger' and the resource 'hot reload', and distinguishes itself from sibling tools like flutter_hot_restart by emphasizing state preservation.

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 advises calling flutter_connect first, providing a prerequisite. It also implicitly suggests use when needing fast iteration, but does not explicitly state when not to use it (e.g., for full restart) or list alternatives.

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