ue_console_command

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

Explains that commands don't return values but write to log, and the tool captures new log lines. Also notes it uses the editor's Python interpreter, not the Remote Control API, and can execute even 'quit'. No annotations provided, so description carries full burden and does well.

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?

Description is moderately concise, with multiple paragraphs that could be slightly tightened. However, it front-loads the main purpose and provides necessary details without excessive verbosity.

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?

Given no output schema, the description explains the return value (new log lines) and covers all essential aspects: purpose, behavior, parameters, and useful examples. It is sufficiently complete for an agent to use the tool effectively.

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 has 0% description coverage, but description adds meaning: 'command' is illustrated with an example ('stat fps'), and 'wait_seconds' is explained as time to wait for log output. This compensates for the schema gap.

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 an editor console command and returns its output, with specific examples like 'stat unit' and 'r.ScreenPercentage 50'. Distinguishes from sibling tools like ue_exec_python by focusing on console 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?

Provides examples of useful commands and contrasts with Remote Control API pathway. However, it does not explicitly state when not to use or suggest alternatives, though the context implies it's the preferred method for console commands.

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