session_record_stop

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

With no annotations, the description must carry the full burden. It discloses the core side effect ('Stop a recording session') and the return value (event count and duration). It does not mention whether stopping is destructive/final, whether it persists captured events, or error behavior for non-existent sessions, so transparency is adequate but incomplete.

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?

A single, front-loaded sentence that states the action and the result with no filler. Every word contributes to the agent's understanding.

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 tool with no annotations and no output schema, the description gives the essential action and return value, and the schema covers the parameter. Still, the agent is left to infer lifecycle requirements (active session, relationship to session_record_start) and failure behavior, which would matter for correct invocation.

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 100% and the sessionId parameter is already documented ('Session to stop; required only when multiple recordings are active'). The tool description adds no parameter-level meaning, so the baseline of 3 applies.

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?

Description opens with the specific verb 'Stop' and identifies the resource ('a recording session'), and it adds the distinctive outcome 'return the captured event count and duration.' This cleanly separates it from the session_record_start/list/events/replay siblings even without naming them.

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 intended trigger is implied by the verb 'Stop': use this when an active recording should be ended. However, the description never states prerequisites (e.g., a prior session_record_start), when the optional sessionId is needed beyond the schema note, or what to do if no recording is active. It is implied usage, not explicit guidance.

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