run_console_command

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 discloses that a console command is executed, but does not mention potential side effects, whether arbitrary commands can modify editor state, how output is returned, or any safety considerations. For a generic command execution tool, this is a significant transparency gap.

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 with no filler. Every word adds meaning, and the core execution target and context are immediately clear.

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?

This is a simple one-parameter tool with an output schema, so structural details like return values need not be described. However, given the open-ended nature of console commands and the absence of annotations, the description would benefit from noting that commands are executed verbatim and may have arbitrary side effects on editor state. It is minimally adequate but incomplete for safe use.

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 0%, so the description must compensate. It clarifies that the 'command' parameter is an O3DE console command rather than a shell command, but it does not explain command syntax, argument formatting, or where to find valid commands. This is minimal added meaning beyond the schema's own 'Command' property name.

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 states a specific verb ('Execute'), a clear resource ('O3DE console command'), and the execution context ('in the running editor'). This is clear enough to distinguish it from siblings like run_editor_python, though it does not explicitly contrast itself with alternatives.

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 gives no guidance about when to prefer this tool over similar sibling tools such as run_editor_python, exec_in_session, or get_cvar/set_cvar. It only says commands are executed in the running editor, with no exclusions or alternative recommendations.

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