stop_recording_screen

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

The description claims to 'stop' a recording and 'return' the video, which is a state-changing operation. However, the annotations declare 'readOnlyHint: true', suggesting the tool is read-only. This is a direct contradiction. Additionally, the description does not disclose side effects (e.g., whether the recording file is deleted after return) or authentication requirements for remote upload.

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 two sentences with no wasted words. The first sentence states the core action, and the second explains the two modes of output. It is appropriately front-loaded and efficient.

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 7 optional parameters and no output schema, the description explains the output format (base64 or remote upload) but fails to cover side effects (e.g., whether the recording is saved or discarded) or provide behavioral context for the large number of upload parameters. It meets the minimum viable but leaves gaps in understanding full behavior.

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%, providing baseline clarity for all 7 parameters. The description adds value beyond the schema by explaining the default behavior (return base64) and the conditional behavior when 'remotePath' is provided. However, it does not elaborate on the remaining upload-related parameters beyond what the schema states.

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 a specific verb ('Stop') and resource ('screen recording'), and clearly states the action and output (return the video). It distinguishes itself from its sibling 'start_recording_screen' by focusing on stopping and returning the recording.

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 does not provide guidance on when to use this tool vs. alternatives, such as needing to call 'start_recording_screen' first. There is no mention of prerequisites or when not to use it, leaving the agent without decision-making context.

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