rec_stop

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

Annotations already declare non-readonly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: ADS notifications are released, the file is finalized, status+stats are returned, and the Scope holder is prompted (scope_next) to close, restart, or pause. The Scope sentence is somewhat garbled, but the side-effect disclosure is real.

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 core sentence is efficient and front-loaded, but the Scope clause is convoluted and reads as if truncated mid-thought, forcing the agent to parse ambiguous phrasing to understand post-stop behavior.

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?

An output schema exists, so return values ('status + stats') need not be detailed further, and annotations carry the mutation safety profile. The remaining gap is the unexplained 'id' parameter, which leaves the calling contract ambiguous for a one-required-param tool.

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 0% and the only parameter, 'id', is never mentioned in the description. An agent cannot tell whether this is a recording id, session id, or profile id without guessing, so the description fails to compensate for the undocumented 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+resource: stop a recording, release ADS notifications, finalize the file. It conveys the effect clearly, though it doesn't distinguish itself from the nearby rec_profile_stop or rec_start siblings by name.

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?

There is no explicit guidance on when to call this versus rec_profile_stop, rec_start, or rec_delete. The Scope sentence describes what happens after stopping, not the condition that selects this tool over alternatives.

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