Stop recording LCU WAMP traffic

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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description's 'Idempotent; safe to call when already stopped' largely restates the annotation; the only genuinely additive behavioral fact is that captured entries persist and can be retrieved via the dump tool.

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?

Three short sentences, each earning its place: purpose first, then the usage trigger, then the retrieval path and safety note. No filler or restated tool name beyond the opening verb.

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 zero-parameter stop tool with rich annotations and no output schema, the description covers what it does, when to call it, that it is safe to repeat, and where the captured data lives afterward. Nothing an agent needs to invoke it correctly is missing.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter detail where none exists.

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?

States a specific verb and resource: 'Terminate the dedicated WAMP recorder WebSocket connection and halt traffic capture.' This clearly distinguishes it from the sibling lol_wamp_record_start and lol_wamp_record_dump without needing to open any schema.

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?

Explicitly names the trigger ('when WAMP diagnostic recording is finished') and routes the agent to the correct alternative for retrieving results ('Recorded entries remain accessible via lol_wamp_record_dump'). It also pre-empts the redundant-call question by noting it is safe to call when already stopped.

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