Stop recording

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

The description adds substantial behavior beyond the annotations: it opens the editor, explains that cloud recordings are already uploading with videoId and links, and local recordings are saved as takeId for later upload. It also notes that placed markers are returned, giving an agent useful side-effect and return-shape context.

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 action and then explains the immediate consequence and return structure. It is dense but every sentence earns its place, especially because no output schema is provided.

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 one-parameter stop action with no output schema, the description covers what happens, where the recording goes, and the follow-up for local recordings. The remaining timeout details are handled by the schema.

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 100%, so timeoutMs is already fully documented in the input schema. The description does not add meaning to the timeout parameter, focusing instead on return values and side effects.

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?

States a specific verb and resource: stop the current Recordful recording. It also places the action in the sibling lifecycle by distinguishing stop from start/pause/resume, and names upload_recording for the local case.

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 usage context is clear: call it when the current recording should end, and Recordful will open its editor just like clicking Stop. It names upload_recording as the follow-up for local recordings, but it does not explicitly state when not to use this tool or discuss timeout behavior.

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