restart_service

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

Discloses the stop-then-start sequence and safe mode restrictions. No annotations provided, so description carries full burden. Still lacks details like permissions required, impact on existing connections, or error handling (e.g., if service doesn't exist).

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 short sentences with no redundant information. First sentence defines action, second adds important constraint. Front-loaded and efficient.

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?

Tool is simple with only two parameters and no output schema. Description covers basic behavior and a safety constraint. Missing notes on what happens in safe mode if blocked, or return values (though no output schema). Adequate but not thorough.

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 100%, so baseline 3. Description adds no additional meaning beyond what the schema already provides for parameters 'server' and 'service'. No examples or clarifications.

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?

Description clearly states it restarts a system service by stopping then starting it. It also adds a safety note about critical services possibly being blocked in safe mode. However, it does not explicitly distinguish from sibling tools like start_service or stop_service.

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?

No guidance on when to use restart versus stop+start separately or alternatives. The safe mode warning is a constraint but not a usage criterion. Missing when-not-to-use or prerequisites.

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