qt_record_stop

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

With no annotations provided, the description carries the full behavioral burden. It discloses that stopping returns a GIF, implying finalization, but it does not mention side effects such as what happens to the recording session, error behavior for invalid IDs, or whether stopping is destructive.

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 front-loaded with the core action and return value, followed by a concise argument note. Every sentence contributes directly to invocation.

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?

The tool is simple with one required parameter, and an output schema exists so return format details are not needed in the description. The description covers the action, prerequisite, and parameter origin adequately, though it could note error or edge-case behavior.

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?

Although schema description coverage is 0%, the description explains that recording_id is the identifier returned by qt_record_start and that it includes the associated app. This adds meaningful context beyond the bare string schema.

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 uses a specific verb and resource ('Stop a recording') and explicitly ties it to the sibling tool 'qt_record_start', so an agent can distinguish it from related capture tools like qt_record_gif. It also names the returned artifact (GIF), clarifying the outcome.

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?

It clearly states the tool is for stopping a recording that was started with qt_record_start, giving the agent a prerequisite context. However, it does not explicitly mention alternatives or when not to use it (e.g., if no recording is active).

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