MCP Scrcpy Vision

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions stopping a pipeline and removing a resource, which implies a destructive action, but fails to detail side effects (e.g., whether it terminates processes abruptly, frees memory, or requires specific permissions). This is inadequate for a tool that likely involves system-level operations.

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 directly states the tool's action without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly for its core purpose.

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 stopping a vision stream (likely involving system processes), no annotations, no output schema, and low schema coverage, the description is insufficient. It lacks details on behavior, error handling, or what happens post-execution, making it incomplete for safe and effective use by an AI agent.

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 1 parameter with 0% description coverage, and the tool description adds no information about the 'serial' parameter's meaning or format. Since schema coverage is low, the description should compensate but does not, resulting in a baseline score of 3 due to the minimal parameter count, though it misses an opportunity to clarify usage.

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 ('stops') and target ('scrcpy + ffmpeg pipeline and removes the frame resource'), which aligns with the title about stopping a vision stream. However, it doesn't explicitly differentiate from sibling tools like 'android.vision.startStream' beyond the obvious stop vs. start distinction, missing nuance about when to choose one over the other.

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, such as indicating it should only be called after starting a stream with 'android.vision.startStream' or in scenarios where stopping is necessary to free resources. It lacks context about prerequisites or exclusions, leaving usage ambiguous.

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