Виконати довільну команду Minecraft-сервера

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 does disclose RCON transport, automatic leading-slash handling, and raw server text output. However, for an arbitrary command execution tool, it does not warn about full console privileges, irreversible side effects, or potentially destructive commands beyond using the word "ANY".

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?

Three dense, front-loaded sentences cover the action, the exact invocation convention, the relationship to sibling tools, and the return behavior. No filler or repetition of schema content.

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?

Without an output schema, the description correctly explains what is returned: raw server text output. It also covers the key distinction from siblings. It could be slightly more complete by mentioning risk or permission implications of RCON, but the core calling context is present.

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 only 50% because the required command parameter has no schema description. The tool description compensates by explaining that the command should not include a leading slash and that one will be added if present, which is critical semantic guidance. The timeout parameter is adequately described in the schema itself.

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 executes any vanilla or plugin command via RCON, which is a specific verb and resource. It explicitly distinguishes itself as the most general tool, covering everything not handled by structured mc_* tools, and gives concrete examples like /gamemode and /effect.

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?

Usage context is explicit: use this tool for anything not covered by the structured mc_* siblings, with examples of fallback scenarios. The description makes the selection rule clear without requiring the agent to inspect other tools.

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