ue5_execute_console_command

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

The description adds important behavioral information not in annotations (which are absent) by noting that UE5 does not return success/failure and the response is always empty. This is critical for the agent to manage expectations. However, it omits other behavioral aspects like potential side effects or prerequisites (e.g., an open project).

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 extremely concise: a single sentence and a note. It is front-loaded with the action and resource, and every word serves a purpose.

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 covers the key aspects: what the tool does and the notable behavioral detail about empty responses. It is fully adequate for the tool's complexity.

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 coverage is 100% and the schema already provides examples for 'command'. The description does not add any new information beyond what is in the schema, meeting the baseline of 3.

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 verb 'Executes' and the resource 'Unreal Engine console command in the editor', making the tool's purpose very specific and distinct from siblings like ue5_build_lighting or ue5_call_function.

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 this tool is for executing console commands, but it does not explicitly state when to use it versus alternatives or provide any exclusions. The note about empty responses is helpful for usage but not a guideline on context.

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