stop_screen_record

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions stopping recordings but doesn't disclose what happens to the recording file, whether this requires specific permissions, if it works across all devices, or what the expected outcome is. The description is too sparse for a mutation tool.

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 extremely concise with a single, clear sentence that states the core functionality upfront. There's no wasted verbiage or unnecessary elaboration, making it easy to parse quickly.

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 this is a mutation tool with no annotations, 0% schema description coverage, but with an output schema present, the description is minimally adequate. The output schema will provide return value details, but the description lacks important context about behavior, prerequisites, and relationships with sibling tools.

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?

With 0% schema description coverage for the single parameter (device_serial), the description adds no parameter-specific information. However, since there's only one optional parameter, the baseline is appropriately high. The description implies the tool works without parameters to stop 'any' recording, which aligns with the optional nature of device_serial.

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 ('Stop') and target ('any ongoing screen recording'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'start_screen_record' or 'pull_recordings' beyond the obvious opposite function.

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, prerequisites for use, or what constitutes 'ongoing screen recording.' It doesn't mention the relationship with 'start_screen_record' or other recording-related tools.

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