select_worker

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

No annotations are provided, so the description carries full burden. It discloses the behavior of clearing the realm with an empty string, which is useful. However, it does not mention potential side effects, error conditions (e.g., invalid realm ID), or whether the operation is idempotent. For a tool with zero annotations, more behavioral detail would be warranted.

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 extremely concise: two sentences with no wasted words. The first sentence states the primary action, and the second provides additional context. It is front-loaded and 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 tool's low complexity (1 parameter, no output schema, no nested objects), the description covers the essential aspects: purpose, usage, and a special behavior. It is missing a brief note about parameter format or return value, but for a simple setter tool, this is largely sufficient.

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?

The input schema has one required string parameter 'workerRealmId' with 0% description coverage in the schema. The description adds important meaning: 'Pass empty string to clear.' This clarifies that an empty string is a valid input for clearing, which is not obvious from the schema alone. It does not, however, explain what constitutes a valid non-empty realm ID.

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 action ('set'), the resource ('active worker realm'), and includes a special case ('pass empty string to clear'). It also mentions its role as default target for hook tools, distinguishing it from sibling tools like select_frame and select_page.

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 context on when to use this tool: 'Used as default target by hook tools.' This implies that select_worker should be called before using hook tools. It lacks explicit 'when not to use' or alternatives, but the guidance is clear.

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