server_restart

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 usefully discloses the non-obvious ssl behavior (preserving the current scheme), but it does not mention potential downtime or other side effects of a restart. This goes beyond a bare statement but lacks rich detail.

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 compact: one sentence defining purpose and a brief parameter explanation. No padding, every sentence contributes to understanding the tool and its single argument.

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 tool with one optional parameter, the description covers the purpose and parameter semantics effectively. Since an output schema exists, return values need not be described in the text. Minor omissions like downtime impact are acceptable given the tool's simplicity.

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's 'Args' section fully compensates by explaining the ssl parameter in detail: it can enable HTTPS, and when left unset it preserves the existing scheme. This adds substantial meaning beyond the schema's bare type definition.

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 opens with 'Restart the server to pick up new or edited transform modules,' clearly stating the verb, resource, and purpose. This distinguishes server_restart from sibling tools like server_start, server_stop, or server_status, which have different actions.

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 phrase 'to pick up new or edited transform modules' provides clear context for when to use this tool. It does not explicitly name alternatives or exclusions, but the purpose is clear enough to differentiate it from related server operations.

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