flutter_run

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'hot reload enabled', which hints at interactive development behavior, but lacks details on permissions, side effects (e.g., if it starts a server or modifies files), error handling, or runtime characteristics. This is inadequate for a tool that likely initiates a complex development process.

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 a single, efficient sentence that front-loads the core action and key feature ('hot reload enabled') with zero wasted words. It is appropriately sized for the tool's complexity and easy to parse.

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 complexity of starting a Flutter development session, no annotations, and no output schema, the description is insufficient. It lacks details on what the tool returns (e.g., process ID, logs), how it behaves over time, or dependencies, making it incomplete for effective agent use in a development context.

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?

Schema description coverage is 100%, so the schema fully documents all five parameters. The description adds no parameter-specific information beyond what's in the schema, such as examples or constraints. Baseline 3 is appropriate as the schema handles the heavy lifting, but the description doesn't enhance parameter understanding.

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 action ('Start') and resource ('Flutter development session') with a specific feature ('hot reload enabled'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'flutter_dev_session' or 'flutter_build', which could have overlapping or related functionality.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'flutter_dev_session', 'flutter_build', and 'flutter_test', there is no indication of context, prerequisites, or exclusions for using 'flutter_run', leaving the agent without usage direction.

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