payload_host_stop

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

No annotations are provided, so the description carries the full burden. It simply repeats the action without disclosing side effects, reversibility, or behavior when no host is running. For a stopping action, more transparency (e.g., 'stops the current HTTP server, making payloads inaccessible') would be expected.

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, short, front-loaded sentence: 'Stop payload HTTP host.' Every word earns its place; no fluff 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?

Given the tool's minimal complexity (no parameters, no output schema, no annotations), the one-line description is nearly complete. It clearly states the action and target. Minor gaps include lack of mention about idempotency or post-stop state, but for this simple tool the description suffices.

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 input schema has zero parameters, and the description correctly adds no parameter information. According to the rubric, 0 params baselines at 4, and there is nothing else 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 uses a specific verb 'Stop' and explicit resource 'payload HTTP host', clearly indicating the action. It distinguishes from sibling tools like payload_host_start and payload_generate by being the inverse operation. No ambiguity about what the tool does.

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?

Usage is implied by the description and the sibling tool payload_host_start: use this to stop the host started with payload_host_start. However, it does not explicitly state when to use it vs alternatives, nor provide any exclusions. The guidance is minimal but not absent.

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