ue_console_command

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

Annotations provide readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds that it captures output and lists blocked destructive commands, but does not disclose other behavioral traits such as side effects, error behavior, or permissions. The annotations carry the main transparency burden.

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 with two sentences, no extraneous words, and front-loads the core purpose. The blocked command list adds value without bloat.

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?

Given a single parameter and an existing output schema, the description covers the essential action. However, it lacks information on error handling, execution context (e.g., UE editor), and potential timeout behavior, making it only 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 has 0% description coverage, and the tool description does not explain the 'command' parameter at all. It only mentions 'Execute a UE console command,' which is insufficient to convey what values the parameter accepts or any format requirements.

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 UE console command and capture output,' using a specific verb and resource. It distinguishes from siblings like ue_execute_python by listing blocked commands, which narrows the scope.

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 lists blocked commands (e.g., exit, quit, crash), which provides when-not-to-use guidance. However, it does not explicitly state when to use this tool over alternatives like ue_execute_python, leaving gaps in usage context.

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