Stop recording a live call

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds real behavioral context the annotations lack: the operation only applies to a LIVE call and the omit-url form fans out to all recordings on that call. It stops short of saying what happens to the audio once stopped.

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 and its live-call constraint are front-loaded, followed immediately by the parameter branching rule.

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 2-param mutation with no output schema and full annotation coverage, the description supplies the key precondition and parameter behavior an agent needs. Minor gap: no mention of error behavior when the call is not live or has no active recording.

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 only 50% (call_uuid is undocumented), but the description compensates for the url parameter by explaining its provenance (returned by start_recording) and its default behavior when omitted, which is more than the schema's terse field description provides.

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 (stop), resource (recording) and scope (on a LIVE call), plus the underlying endpoint DELETE /Call/{uuid}/Record/. This distinguishes it from siblings like stop_conference_recording and delete_recording without needing to open a schema.

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?

Gives clear conditional guidance: pass the url returned by start_recording to stop one recording, omit it to stop all recordings on the call. It does not, however, explain when to prefer this over delete_recording (stopping a live capture vs. removing a stored file), leaving one sibling relationship to inference.

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