ue_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 that any console command is supported, but it does not warn about potential side effects such as modifying editor state, crashes, or the need for a running editor session. For an arbitrary-command execution tool, this is a significant 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 focused sentence followed by a short list of examples. It is front-loaded with the core purpose and adds useful context without any unnecessary verbosity or repetition.

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 is simple with one parameter, but the description does not mention return values or output format, and there is no output schema to compensate. It also lacks context about prerequisites like a running Unreal Engine project. The description is minimally sufficient but could be more complete for an arbitrary-command tool.

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 already provides 100% coverage for the single parameter, so the baseline is 3. The description adds value by listing common command examples ('stat fps', 'show collision'), which helps the agent understand what to pass and what kinds of commands are available.

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 a specific verb (execute) and resource (console command in Unreal Engine). It also distinguishes this tool from siblings by noting it supports any command available in the editor console (~), making its scope explicit.

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 running editor console commands and lists common examples, but it does not explicitly state when to use this tool versus alternatives or when not to use it. Since no sibling tool appears to serve the same purpose, the context is implied rather than fully explicit.

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