flutter_connect

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that relaunch 'force-stop[s] and restart[s] the app,' that the VM Service URI is only emitted at launch, and that connectivity is limited to debug/profile builds. It does not cover connection lifecycle (e.g., whether flutter_detach is required), but the main side effects and constraints are stated.

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 tight and front-loaded: the core action and 'call this first' come in the opening sentence, followed by a short context paragraph and a compact Args list. No sentence is redundant.

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 annotations are absent and the schema carries no descriptions, the tool definition supplies the necessary prerequisites (logcat-only URI, debug/profile builds), the optional relaunch behavior, and parameter semantics. An output schema exists, so omitting return-value details is acceptable; the only minor gap is not explaining what later tools require this connection.

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 0%, so the description must compensate, and it does: package is explained as 'application id, needed for relaunch,' relaunch as 'force-stop and restart the app to capture a fresh URI,' and serial as 'device serial when several are attached.' Each parameter's purpose and condition is clearer than the bare schema.

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 uses the specific verb 'Connect' with a defined resource, 'a running Flutter app's Dart VM Service,' and adds the sequencing instruction 'Call this first.' It does not explicitly distinguish itself from the sibling tool flutter_attach, so it falls short of the highest bar, but the target and action are unmistakable.

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?

It gives explicit context: the URI appears only in logcat at launch and only for debug/profile builds, and relaunch=True is the workaround when it has scrolled out of the buffer. This explains when the optional destructive path should be taken, though it does not name alternatives such as flutter_attach or state when not to use this tool.

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