zen_focus_window

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

Description gives only one action without disclosing behavior: what happens if the window doesn't exist, permissions needed, or whether it brings to front or requests focus. No annotations exist to supplement.

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 brief (one sentence), but it sacrifices essential information for conciseness. It fails to provide parameter details or behavioral context.

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 single required parameter and no output schema, the description is incomplete. It does not explain the parameter, return behavior, or error handling, making it insufficient for an agent to use correctly.

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 parameter 'window_id' with 0% description coverage. The description does not explain what 'window_id' is or how to obtain it, leaving the agent without necessary context.

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: 'Bring a browser window to the foreground.' It specifies a verb and resource, distinguishing it from unrelated tools. However, it does not differentiate from siblings like 'zen_focus' or 'zen_wake_tab'.

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 guidance is provided on when to use this tool vs alternatives, such as 'zen_focus' or 'zen_switch_tab'. There is no mention of prerequisites or context.

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