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

No annotations are provided, so the description carries the full behavioral-disclosure burden, but it only states the elementary action "Stop session replay." It omits whether stopping is destructive, what happens to the capture job, required permissions, idempotency, and post-stop state.

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 a single short sentence with no wasted words, but it is under-specified rather than genuinely informative. Its brevity leaves no structure for guiding correct invocation.

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 mutation-style stop operation with no annotations and no output schema, the description should disclose side effects, state changes, or return behavior. It provides none of that, leaving the agent dependent on the name and parameter schema alone.

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?

The schema has 100% description coverage for both parameters, including the required captureJobId. The description adds no parameter meaning, but under the rubric this is the baseline when the schema already documents the inputs.

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 is a bare restatement of the tool name: "Stop session replay." It identifies a verb and resource, but adds no scope, effect, or sibling differentiation beyond what the name already conveys, making it effectively tautological.

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 when-to-use guidance, no prerequisites, and no named alternatives. It does not clarify when to use stop_session_replay versus start_session_replay, stop_manual_recording, or pause_capture.

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