execute_console_command

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Run a console command' without mentioning potential side effects, that arbitrary commands may modify editor state, or whether output is returned. This is insufficient for a mutating action, especially given no annotations.

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, front-loaded sentence that gets straight to the point. Every word is necessary, with examples that are brief and illustrative. No fluff or redundant 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?

For a simple tool with one parameter and no output schema, the description is adequate but lacks details about return behavior, authentication, or potential limitations. Given the existence of a sibling run_stat_command, the description could clarify its scope further, but it is minimally 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 schema fully documents the 'command' parameter, and the description adds concrete example commands ('stat fps', 'stat unit', 'r.SetRes 1920x1080') that clarify the expected string format, providing value beyond the schema.

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?

The description clearly states the tool runs console commands in the Unreal Editor, with specific verbs ('Run'), resource ('console command'), and concrete examples. It distinguishes from siblings like execute_python (Python execution) and run_stat_command (likely a subset) by being the generic console command tool.

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?

The description implies usage for any console command via examples but does not explicitly state when to use this over the sibling run_stat_command, which might be more appropriate for stat commands. There are no explicit exclusions or mentions of alternatives, leaving the selection ambiguous.

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