screen_record_stop

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

Annotations say idempotentHint=true, indicating stopping a non-existent recording is safe, and destructiveHint=false. The description confirms the read/pull behavior but adds little beyond annotations. There's no contradiction. The annotation set already covers safety profile; the description adds the 'pull file' behavior context.

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?

One concise sentence, front-loaded with the main action, and captures the key optional behavior. No wasted words. Slightly more detail on usage context could help, but the length is appropriate.

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?

Has an output schema which partially reduces the need to describe return values. However, for a stop/cleanup operation, it would help to mention whether stopping implies a timeout, what happens if no recording is active (idempotent per annotations), and any interaction with the host pull in case of failure. Adequate but with room to enrich.

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%, so parameters are well-documented in the schema itself. The description adds minimal value — it mentions 'pull the file to the host' which maps to pullToHost, but doesn't expand beyond the schema's parameter descriptions. Baseline 3 is appropriate given full schema coverage.

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 a clear verb+resource: 'Stop screen recording and optionally pull the file to the host.' It distinguishes from screen_record_start, though there's also stop_video_stream in the sibling set which could create ambiguity — the description doesn't clarify the distinction between stopping a screen recording vs. stopping a video stream.

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 it's the end-phase companion to screen_record_start, and mentions the optional pull-to-host behavior. However, it doesn't explicitly say when to use it (only after screen_record_start), doesn't specify prerequisites, and doesn't clarify the screen_record_stop vs stop_video_stream distinction.

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