stop_all_recordings

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

No annotations are provided, so the description must disclose behavioral traits. It mentions filtering by target and response grouping, but does not explicitly state the destructive nature (e.g., loss of unsaved data) or how recordings are terminated. Some behavioral context is given, but more transparency would improve agent understanding.

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 four sentences with no unnecessary words. Each sentence serves a distinct purpose: main action, use cases, parameter guidance, response structure. Front-loaded with the primary function.

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 the simplicity of the tool (one optional parameter, no required fields, output schema exists), the description covers all key aspects: when to use, how to filter, and what the response contains. It does not list all possible aliases but references start_recording, which is acceptable.

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% with a clear description for the single parameter. The description adds value by listing example aliases ('macos, ios_simulator, android') and explaining the effect of omitting the parameter, which goes beyond the schema's description.

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 all live recording sessions', specifies the context 'for this server process', and distinguishes from the sibling stop_recording by emphasizing 'all' sessions. The verb and resource are specific and unambiguous.

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?

Explicit use cases are provided: client lost session_id, duplicate-target protection blocking start_recording, or before a fresh verification run. This gives clear guidance on when to invoke this tool versus alternatives.

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