ue_select_actors

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

With no annotations, the description carries the burden of disclosing behavior. It explicitly states that by default the selection is replaced and that addToSelection=true adds to the existing selection. This is the key behavioral trait for a selection tool. It doesn't discuss return values or side effects, but none are critical for this simple operation.

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 two sentences with no wasted words. It leads with the primary purpose, then immediately clarifies the parameter behavior. Every word earns its place, and the structure is easy to parse.

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 two parameters and no output schema, the description covers everything needed: what it does, the default behavior, and how to opt into additive selection. It is self-contained and sufficient for an agent to invoke correctly without external context.

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%, with parameter descriptions for actorPaths ('Array of actor paths to select') and addToSelection ('Add to existing selection'). The description adds semantic value by explaining the default behavior (replaces) and how to modify it using addToSelection=true, deepening the meaning beyond the schema's brief labels.

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 tool selects actors in the Unreal Editor, with a specific verb ('Select') and resource ('actors'). It also distinguishes the default behavior (replace current selection) from the alternative (add to selection), which sets it apart from sibling tools like ue_get_selected_actors.

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 provides clear context for when to use the tool: when you need to select actors, with the default replacing the current selection and addToSelection=true for adding. It doesn't explicitly exclude alternative tools, but the purpose and behavior are clear enough for an agent to select this appropriately among siblings.

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