record_stop

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions stopping and saving to disk, implying finality, but does not elaborate on irreversibility, state effects, or whether the recording is deleted after saving. It is adequate but not comprehensive.

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 extremely concise with two sentences clearly stating the purpose and parameter guidance. No superfluous information; every word 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?

Given that an output schema exists, return value documentation is not needed. The description is minimal but sufficient for a straightforward stop command, covering the key aspect of the parameter source. It lacks only minor behavioral details.

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 0%, so the description must compensate. It adds meaning by stating that output_path is 'the path returned by record_start', which tells the agent the origin and context of the parameter, beyond the schema's title 'Output Path'.

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 action 'Stop the PipeWire recording and save to disk', identifying the specific resource (PipeWire recording) and the verb (stop, save). It distinguishes itself from sibling tools like record_start by being the obvious counterpart.

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 usage after record_start by specifying that output_path comes from record_start. However, it does not explicitly state when not to use it or provide alternative options, relying on the context of sibling tools.

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