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

It discloses the core behavioral effects (focus and app activation), the permission requirement, and the window_not_found error case. This adds useful context beyond the sparse annotations and does not contradict them.

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 short sentences deliver purpose, input source, error case, and permission in order of importance. There is no filler or redundancy.

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 single-parameter tool with no output schema and minimal annotations, the description covers everything an agent needs to call it correctly: action, input provenance, permission, and failure mode.

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 schema already fully describes window_id with its source and error behavior. The description repeats this information without adding extra semantic detail, so it meets the baseline for 100% schema coverage.

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 states a specific action—brings a window to the front and activates its app—and ties the input to list_windows. This clearly distinguishes it from related tools like window_set_frame or ui_* actions.

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 gives clear usage context: use a window_id from list_windows to bring that window to the foreground. It also notes a prerequisite (Accessibility permission), though it doesn't explicitly compare against alternatives like window_set_frame.

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