capture_stop

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

Annotation Contradiction: The description says the tool will 'discard its buffer,' which is a destructive loss of captured data, but annotations declare destructiveHint=false. This directly contradicts the annotation and obscures the tool's real effect.

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?

One concise sentence with no wasted words. The action is front-loaded and the side effect is stated directly.

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 tool is simple and has an output schema, so return value explanation is unnecessary. However, the contradiction about destructiveness leaves the behavioral contract unclear, and there is no mention of lifecycle context or what happens with an invalid/expired session.

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 0%, and the description does not explain where session_id comes from or what format/state it should be in. The phrase 'capture session' provides some semantic link, but it is not enough to compensate for the missing schema documentation.

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') and resource ('capture session'), and adds a clarifying side effect ('discard its buffer'). This makes it clearly distinct from siblings like capture_start, capture_read, and capture_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 intended use case is implied: stop a capture session when you no longer need it. However, the description does not explicitly say when to use this tool versus alternatives, nor does it note prerequisites such as reading the buffer before stopping if the data is needed.

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