stop_screen_recording

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the action and that the result is saved as an MP4, but it does not mention error behavior if no recording is active, file destination, or any permissions/requirements. This is a minimal disclosure that leaves important behavioral aspects unexplained.

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, focused sentence that front-loads the key action ('Stop') and provides a necessary detail ('save the MP4'). It wastes no words and is appropriately sized for the tool's simplicity.

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?

While an output schema exists, the description still lacks context about device identification, prerequisites, error conditions, and side effects. For a simple stop action, it covers the core function, but the absence of behavioral detail and parameter guidance makes it incomplete for an agent to use confidently.

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 schema has 0% description coverage for the single 'device' parameter, and the description does not compensate by explaining what 'device' refers to or its expected format. Since there is no parameter information in either the schema or the description, the agent has no guidance on how to provide this value.

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 verb 'stop' and the resource 'device screen recording', then adds the outcome 'save the MP4'. This distinguishes it from sibling tools like start_screen_recording and screen_recording_status, making the purpose unambiguous.

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?

No explicit guidance is given about when to use this tool versus alternatives. The mention of 'running device screen recording' implies a prerequisite, but there is no reference to sibling tools or conditions under which this should be called. The agent is left to infer usage.

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