stop_app

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

No annotations are provided, so the description carries the full burden. 'Stops the currently running Flutter app and cleans up' implies destructive action, but 'cleans up' is vague - it doesn't specify what gets cleaned up (processes, session state, emulator state?), whether the flutter tool remains connected, or what happens if no app is running. Some context is implied but not specified.

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?

A single concise sentence. Efficient and to the point. Could arguably be criticized for being under-specified, but for a zero-parameter tool, it's appropriately brief.

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?

The tool has 0 parameters and no output schema, making it structurally simple. However, the description doesn't clarify key operational details: is this idempotent? What does 'clean up' entail? How does it interact with start_app or pilot_hot_restart? For a tool that terminates a running process, a bit more behavioral context would help the agent know when and how to invoke it safely.

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?

Tool has 0 parameters, so there are no parameter semantics to describe. A 0-parameter tool doesn't need the description to explain parameters. Baseline 4 is appropriate.

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 states the verb (Stops) and resource (currently running Flutter app) and notes it cleans up. It's clear what it does, but it doesn't distinguish itself from sibling tools like start_recording/stop_recording, though those are clearly different operations. It's adequate but not differentiated from alternatives.

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?

No guidance on when to use this vs alternatives. It doesn't specify whether stop_app is required before starting another app, nor does it explain the relationship with start_app (does it reset state, kill the session?). There is no when/when-not guidance, and it doesn't reference any sibling tool.

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