actiond_server_stop

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

Reveals environment variable requirements, default refusal with a list of pending/running jobs, force behavior with job interruption, no-op behavior, and the return envelope. Consistent with idempotentHint and readOnlyHint annotations.

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?

Four dense but relevant sentences cover all key behaviors without unnecessary detail or repetition.

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?

Even without an output schema, the description states the return envelope format and covers all preconditions, side effects, and edge cases needed to call the tool correctly.

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 only parameter, force, is fully explained in both the schema and description, including its effect of stopping the server even when jobs are executing.

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 action ('Stop the ActionD server daemon') and clearly distinguishes it from sibling lifecycle tools like start and 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?

Provides explicit usage conditions: requires ACTIOND_MCP_ALLOW_LIFECYCLE=1, default protects in-flight work, and force=true overrides that protection. Also notes the no-op behavior for an already-stopped server.

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