Stop a Minehut server

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Power off' without mentioning side effects (e.g., data loss, player disconnects), authentication requirements, or whether the operation is reversible. Lacks important safety context for an agent.

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, compact sentence that conveys the purpose and the accepted parameter format. No redundant words or filler; it is appropriately sized for the tool's simplicity.

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 one-parameter action tool, the description provides the essential purpose and parameter hint but omits behavioral context (e.g., what happens after power-off, whether the server must be online, or how success is indicated). Given no annotations and no output schema, the description is adequate but not fully complete.

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 a single 'server' parameter with no description, but the description adds semantics by clarifying that the parameter can be a name or an id. This helps the agent populate the parameter correctly, though it does not detail exact id formats or validation rules.

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 uses a specific verb 'Power off' with the resource 'Minehut server' and the scope 'by name or id', clearly distinguishing it from siblings like minehut_start and minehut_restart. It directly states what the tool does without ambiguity.

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 explicit guidance on when to use this tool versus alternatives such as minehut_restart or minehut_stop. The intended use is implied by the name and description, but the description does not state prerequisites, exclusions, or alternative tool recommendations.

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