Stop Screen Recording [Pro]

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

With no annotations, the description must disclose behavioral traits. It states the tool stops a recording and optionally pulls the file, but doesn't specify what happens if no recording is active, or if the pull overwrites files. It adds some context beyond the schema but lacks details.

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?

Two sentences, no redundant words. Front-loaded with the main action.

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?

With no output schema and no annotations, the description should cover return values and side effects. It's simple enough that stopping and optionally pulling is clear, but it could mention what happens on success (file path?) or if no recording exists.

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%, so the schema already describes both parameters. The description adds that pull_to_path is optional and for saving locally, which is slightly beyond schema description, but not substantial. Baseline 3 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 clearly states the action (stop recording, save video) and resource (active screen recording). It distinguishes from sibling tools like record_screen and start_test_recording by mentioning 'save the MP4 video' and optionally pulling the file.

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 implies usage when a recording is active and you want to save it, but provides no explicit when-not-to-use or alternatives. For example, it doesn't mention that there's a start_test_recording sibling for test recordings.

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