unity_selection_set

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

No annotations provided, so description carries the burden. It describes the action but does not disclose side effects (e.g., whether previous selection is lost, undo behavior, or if selection change triggers callbacks). With no annotations, a 3 is appropriate as it covers the basic action but lacks deeper behavioral details.

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?

Single sentence, clear and to the point. No wasted words. Could be slightly improved by front-loading key constraints, but it's efficient.

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 the simplicity of the tool (selection set) and no output schema, the description is minimally complete. However, it lacks details like: what happens when multiple parameters are provided (priority/merge behavior), or if selection is cleared. For a straightforward tool, 3 is acceptable but could be more informative.

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 description adds no extra meaning beyond the schema's own descriptions. The schema already describes each parameter (path, paths, instanceId, port). Thus, the description adds minimal value, baseline 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?

Description clearly states it sets editor selection to specific GameObjects. The verb 'Set' and resource 'editor selection' are specific. However, it does not distinguish from sibling tools like unity_selection_get or unity_selection_find_by_type, which are related selection tools.

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?

No explicit when-to-use or when-not-to-use guidance. The description does not mention alternatives. The port parameter description hints at parallel-safe usage, but overall usage context is implied rather than stated.

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