Stop async display recording

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

Discloses the use of SIGINT, artifact creation, and return format. Annotations already indicate non-read-only and non-destructive; the description adds process details beyond annotations.

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?

Single sentence that is front-loaded and concise, with no superfluous words. Every part earns its place.

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?

Describes core behavior but omits prerequisites (must have an active recording started by mobile_record_start) and does not elaborate on 'marks' or 'offsets' despite having an output schema. Adequate for a simple tool but could be more helpful.

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 50%, and the description adds no parameter-specific meaning. It does not explain recordId beyond what the schema provides (pattern, no description). Baseline of 3 for moderate coverage, but fails to compensate for low 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 clearly states the tool stops a screen recording using SIGINT, pulls the resulting MP4 into artifacts, and returns marks with offsets. This is specific and distinguishes it from siblings like mobile_record_start.

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 on when to use this tool vs alternatives (e.g., it should follow mobile_record_start). Requires a recordId, but prerequisites are not stated.

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