Appends a new empty option to a UEnvQuery asset and returns its index along with the total option count. Use to extend EQS queries with additional options.
Appends a new empty option to a UEnvQuery and returns its index.
Returns: { query_path, option_index, option_count }
| Name | Required | Description | Default |
|---|---|---|---|
| query_path | Yes | /Game/... path to the UEnvQuery asset (required) |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false and destructiveHint=false, and the mutation verb 'appends' is consistent with them. The description usefully adds the return shape (query_path, option_index, option_count) but omits whether the change is persisted or requires a separate save step.
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?
Two compact sentences with the action front-loaded and the return contract stated immediately after. No filler.
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?
There is no output schema, and the description compensates by naming the returned fields, which is valuable. What remains missing is prerequisite context (existing query asset, save semantics), keeping it short of a 5.
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 100% with a single documented query_path parameter, so the schema carries parameter meaning. The description adds nothing beyond implying which query is targeted, so the baseline of 3 applies.
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?
States a specific verb (appends) and resource (a UEnvQuery option), plus the side effect of returning an index. It is distinguishable from siblings like add_eqs_generator and add_eqs_test, though it does not explicitly name them.
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 only states what the tool does, with no when-to-use guidance, prerequisites (e.g., the query must already exist), or mention of alternatives such as add_eqs_generator or add_eqs_test.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.