Flutter Hot Restart [Pro]

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

The description explicitly states the behavioral trait: 'Restarts the app from scratch, losing all state'. No annotations are provided, so the description carries full burden; it fully discloses the destructive nature. No contradiction with missing annotations.

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 serving a distinct purpose: identifies the tool as Pro, explains behavior, and provides usage guidance. No redundancy or 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 zero parameters, no output schema, and no annotations, the description covers the essential behavior and prerequisite completely. It tells the agent exactly what happens and when to use it. No gaps remain.

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 no parameters (0), and schema description coverage is 100% (trivially, as there are no parameters to describe). The description adds meaning by explaining what the tool does, but since there are no params, the baseline is 4 as per guidelines.

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 restart on a connected Flutter app, and distinguishes it from hot reload by specifying it applies all code changes including static field initializers and global variables. However, the name already conveys the purpose, so no deduction for lack of differentiation from siblings beyond the explicit comparison to hot reload.

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?

Explicitly tells when to use (when hot reload is insufficient) and provides a prerequisite (call flutter_connect first). No sibling named with similar purpose among siblings (flutter_hot_reload is separate), so the alternative is clearly stated.

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