gmod_execute_rcon

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

No annotations are provided, so the description carries the full behavioral burden for an arbitrary remote command execution tool. It does not state that RCON must be enabled/authenticated on the server, that commands can mutate or destroy server state, or what happens on failure or timeout.

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?

A single short sentence that is front-loaded and wastes no words. Its brevity, however, reflects under-specification rather than disciplined concision, since behavioral context is missing.

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 an execution tool with no annotations and no output schema, the description is too thin: it omits prerequisites (RCON enabled, server connected), the destructive potential of arbitrary commands, and how results are returned or observed. An agent cannot safely call it on this text alone.

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 description coverage is 100% and there is only one parameter, whose schema description ('RCON команда для выполнения') mirrors the tool description. The description adds no syntax, formatting, or quoting guidance beyond what the schema already provides, so the baseline 3 applies.

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 (RCON команда) on a named target (Garry's Mod server), so an agent immediately knows what the tool does. However, it gives no differentiation from closely related siblings such as gmod_console_command or gmod_execute_lua, which also run server-side commands.

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?

There is no guidance on when to use RCON execution versus gmod_console_command, gmod_execute_lua, or gmod_connect. The agent must guess which command channel is appropriate based on names alone.

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