execute_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 of behavioral disclosure. It mentions a prerequisite (Adastrea-Director running), which is useful, but it does not disclose potential side effects, whether the command could be destructive, or what output/return behavior to expect. Since console commands can mutate editor state, this omission is notable.

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 is concise and unambiguous. Every word contributes value: the action, the scope, and a critical prerequisite. There is no wasted text.

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?

The tool has a simple single-parameter schema, and the description states its purpose and prerequisite. However, with no output schema, the description does not explain execution results or potential consequences, which leaves some ambiguity for an agent selecting the tool. It is minimally complete for basic selection but lacks depth.

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 input schema provides 100% coverage of the single 'command' parameter with a clear description and examples. The tool description itself adds no parameter-specific details, but the schema already covers this, so the baseline score of 3 is appropriate.

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 'Execute a console command in the Unreal Engine Editor', identifying the specific verb (execute) and resource (console command in Unreal). The prerequisite 'requires Adastrea-Director to be running' adds context that helps distinguish it from other tools. This differentiates it clearly from siblings like run_python_script.

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 when a UE console command needs to be executed, but it does not explicitly state when to use this tool over alternatives or provide exclusions. The prerequisite is mentioned but not presented as a decision guideline. This is adequate but lacks explicit alternative comparisons.

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