Connect to Flutter App [Pro]

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

No annotations are provided, so the description carries the full burden. It discloses that the app must be running in debug or profile mode, and that auto-discovery may fail, requiring manual URL input. This is sufficient behavioral transparency for a connection tool, though it could mention any side effects like network calls.

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 concise (three sentences), front-loading the core purpose and prerequisites, then adding the optional fallback detail. Every sentence serves a purpose without redundancy.

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 is a connection setup with two params and no output schema, the description is mostly complete: it states prerequisites, return values, and fallback. It could mention that device_id is typically from 'list_devices', but that's implied by sibling context. Overall, adequate for its complexity.

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 coverage is 100%, but the description adds value by explaining the role of vm_service_url as a fallback and hinting at its format. For device_id, it simply restates the param name; however, the schema already provides a clear description. The description does not add much beyond the schema for device_id, but the vm_service_url explanation is helpful.

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 that the tool discovers and connects to a running Flutter app via the Dart VM Service Protocol, specifying the required conditions (debug or profile mode). It also mentions the return of connection details like isolate ID and app name, distinguishing it as a prerequisite for other flutter_* tools.

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 instructs to call this before using other flutter_* tools, providing clear usage context. It also mentions an optional param for when auto-discovery fails, which guides conditional usage. However, it doesn't explicitly state when not to use it or list specific alternatives among siblings.

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