Stage Stop

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states the key side effect: an open page remains on screen but loses the live link until a server starts again.

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?

Two sentences, front-loaded with the core action and targeting rule. The second sentence adds a useful behavioral consequence without wasted words.

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 two-parameter stop action with an output schema and no annotations, the description is largely complete. It covers the action, target selection, and main side effect, though it omits error behavior when no server exists.

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 coverage is 0%, so the description must explain the two optional parameters. It does explain that the target can be selected by port or by the server serving `scenes`, and that the only server is targeted when neither is given, but it does not clarify the expected format or meaning of `scenes`.

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 and resource: stopping a stage server. It also clarifies the targeting modes, distinguishing it from sibling tools like stage_start and stage_restart.

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?

It implies the tool is used to stop a server and explains how to choose which server to stop. However, it does not explicitly say when to use this instead of alternatives such as stage_restart or when stopping is inappropriate.

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