cypress_stop

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

No annotations exist, so the description must carry the behavioral disclosure burden. It clarifies that the action is stopping a running test but does not disclose side effects such as whether artifacts are affected, whether the operation is idempotent, or what happens when no test is running.

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 entire description is a single clear sentence that immediately states the action and target. There is no filler or redundancy.

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 no-parameter command, this description is largely enough to know what it does, but it omits edge-case behavior and any return value expectations. Since there is no output schema or annotations, additional detail on what happens when no test is running would improve completeness.

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 has zero parameters, and the empty input schema already covers everything. The description adds no extra parameter semantics, but none is needed.

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 verb ('stop') and a clear resource ('currently running Cypress test'). This differentiates it from sibling tools like cypress_run_spec, cypress_run_all, and cypress_status.

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 implies the condition for use—that a test is currently running—but provides no explicit guidance on when to use it over alternatives or what to do if no test is running. This is implied rather than explicit.

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