Stop Render Capture

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

With no annotations provided, the description carries the burden of behavioral disclosure. It accurately states the core state-changing behavior: stopping a live session, finalizing buffered events, and returning a profileId. However, it does not disclose whether the operation is irreversible, whether calling it on an already-stopped session errors or is a no-op, or whether any cleanup/race conditions apply. This is adequate but not rich.

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, well-crafted sentence that leads with the action, states the mechanism, and lists downstream consumers. No filler, no redundancy. Every clause earns its place.

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?

The description explains the return value (a profileId) and its usability with four sibling tools, which is especially valuable given there is no output schema. It could be more complete by explicitly stating the prerequisite of an active session (e.g., 'must have an active live capture started by run_render_capture or begin_render_analysis'), but the overall context is sufficiently clear for a single-parameter tool.

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 only parameter, sessionId, is already fully documented in the schema as 'The sessionId returned by begin_render_analysis' (100% schema description coverage). The tool description adds no additional semantic meaning about the parameter itself, only mentioning the returned profileId. Baseline 3 applies because the schema does the heavy lifting.

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 uses a specific verb ('stop') with a clear resource ('live render-capture session') and enumerates the outcome ('finalize the buffered events into a render profile'). It also names the sibling tools that consume the returned profileId, making it easy to distinguish from the other render-capture/analysis tools in the sibling list.

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 description clearly implies this is the terminating step for a live capture session, and it explicitly tells the agent what to do with the result by listing the tools that accept the returned profileId. It lacks explicit when-not-to-use guidance (e.g., no active session or already stopped), but the context is strong enough to route correct usage.

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