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

No annotations provided, so description carries full burden. It discloses the SIGTERM-to-remux-pipeline behavior and the reason (valid moov atom), plus lists return fields. This goes beyond a simple 'stops recording' and gives operational insight.

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 filler. The action, mechanism, and return payload are all stated efficiently.

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?

For a single-parameter stop tool with no output schema and no annotations, the description covers input provenance, operational side effect, and return fields. However, it does not clarify how it differs from related sibling tools ios_record_cleanup or ios_actions_record_stop, leaving some ambiguity in a large sibling set.

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 already documents the sole parameter as 'recordingId returned by ios_record_start' (100% coverage). Description echoes this relationship but adds no new format or syntax details, so baseline 3 applies.

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?

Description uses specific verb 'Stop' with resource 'iOS screen recording' and explicitly references pairing with ios_record_start. It clearly identifies what the tool does and distinguishes from other start/stop pairs.

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?

States the tool stops a recording 'started by ios_record_start', establishing the precondition and when to use it. However, it does not explicitly exclude alternatives like ios_record_cleanup or ios_actions_record_stop.

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