activate_window

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

With no annotations, the description carries the full burden and does disclose real behavior: the z-order-dependent dual effect, the GUID rebinding (first-appearance) machinery, and the confirmation criterion (target becomes the last-reported active window). It omits auth/permission needs and any failure/edge behavior, and the density makes the disclosure hard to extract.

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 definition is an unstructured wall of jargon with scattered backticks and parenthetical asides. Only the first sentence is well front-loaded; the rest mixes implementation trivia with the actionable rule, hurting scannability.

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?

An output schema exists, so return values (window_ref, activated, etc.) need not be spelled out. The description covers the core activation semantics adequately, but for a tool with zero schema coverage and no annotations, the missing parameter guidance and permission/edge-case context leave gaps.

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 description coverage is 0%, so the description must compensate for all four parameters. It adds meaning to window_ref ('default the fixture form's app ref') and capture ('replays the genuine navigation from capture'), but host and port are entirely undocumented and even the two covered params are explained only obliquely.

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 opening sentence states a clear verb+resource: 'Bring a buried top-level window to the front natively.' It also distinguishes itself from a sibling, explaining that activate and close are the same command and pointing to close_window. The purpose is legible, though it is soon buried under heavy jargon.

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 explains the contextual behavior (background window activates, active window closes) and cross-references close_window, which is meaningful routing information. However, it gives no clean 'use this when' framing and no prerequisites or exclusions beyond the implicit z-order rule.

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