Set active Roblox client

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

Discloses the primary effect (routing to specified client). With no annotations, it carries the full burden; it adequately conveys the side-effect of switching the active client, though does not detail what happens to the previous active client.

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 sentences with no wasted words; the main action is front-loaded, and the prerequisite advice follows naturally.

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 state-changing tool with no output schema, the description sufficiently explains its purpose and prerequisite. It could mention that changing the active client affects subsequent Roblox tool calls, but this is implied.

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%, so the param is already documented. The description adds value by referencing 'list-clients' for obtaining valid IDs, providing context beyond the schema.

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 it routes future tool calls to a specified client, with a specific verb ('route') and resource ('future Roblox tool calls'). It distinguishes itself from sibling tools like 'list-clients' by implying its role as the routing setter.

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 use 'list-clients' first to get available clientIds, providing clear prerequisite and when-to-use guidance.

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