unity_select_instance

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

Discloses that selection affects all subsequent commands and warns about multiple agents. Lacks explicit statement of non-destructiveness, but context implies it's a session selection, not a mutation.

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?

Concise yet comprehensive: each sentence adds value. Structure logically flows from purpose to prerequisite to parallel safety. No wasted words.

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 one parameter and no output schema, the description covers all necessary information: what it does, how to use it, and important caveats for parallel usage.

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?

Single parameter 'port' is fully described in both schema and description, with clear source (unity_list_instances). No additional information needed.

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 verb 'Select' and resource 'Unity Editor instance', and distinguishes from siblings by noting that subsequent unity_* commands will be routed to the selected instance.

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?

Explicitly instructs to call unity_list_instances first, provides the port parameter, and addresses parallel safety by advising to include 'port' in future calls. No ambiguity.

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