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

Annotations already declare destructive, non-idempotent, open-world behavior, but the description adds important blast-radius detail: only the Minecraft process restarts, players drop for a few seconds, content reloads from Modrinth/CurseForge/download links, and the machine may reboot instead if certain pending changes exist. It also states the online prerequisite and failure condition.

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 front-loaded with the action and player impact, then routing guidance, then fallback and prerequisite conditions. Every sentence adds useful behavioral or selection information with no fluff.

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 destructive restart tool with no output schema, the description covers the important operational context: side effects, when to use it, alternatives, fallback reboot behavior, and the online prerequisite. The only omission is parameter naming, which the schema carries.

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 required path.serverId argument is never mentioned in the description. The schema does include a serverId description pointing to listServers, but with reported schema coverage at 0%, the description does not compensate by explaining the identifier or nested path object.

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 verb and resource: restarting only the Minecraft program on an online server so changed settings apply. It clearly distinguishes this from restartServer, startServer, and restoreBackup by naming the relevant alternatives directly.

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?

Gives explicit when-to-use guidance: when the server reports a restart is required. It also names when-not/alternatives: use restartServer for a size change, startServer if offline, and full reboot may occur for size changes or queued restoreBackup restores.

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