neuron_stop_watch

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

With no annotations provided, the description carries the full burden. It discloses the core behavior and return value, but does not mention what happens if the watchId is invalid, whether stopping is irreversible, or whether accumulated changes are cleared from internal state. This is minimal but not misleading.

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, front-loaded sentence with no filler. It names the action, the target resource, and the return value efficiently.

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 simple one-parameter tool with no output schema, the description covers what the tool does and what it returns. It could mention prerequisite state (an active watch) and failure behavior, but the essential context is present.

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 already covers the single parameter (watchId) with 100% coverage and a helpful description referencing neuron_watch_element. The tool description adds context that stopping the watch yields the accumulated changes, but no additional parameter-level detail is necessary.

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 states a specific action ('Stop watching an element') and a clear deliverable ('return the final list of accumulated changes'). It is immediately distinguishable from paired tools like neuron_watch_element (start) and neuron_get_watches (list active watches).

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 is implied: it is the stopping counterpart to neuron_watch_element and returns accumulated data. However, there is no explicit guidance about when to choose this over neuron_get_watches or neuron_stop_recording, nor any exclusion criteria such as 'only valid for active watch IDs'.

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