manage_window

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

Annotations provide basic traits (readOnly=false, destructive=false, idempotent=true). Description adds action-specific behavior: list/info are reads, resize is a write, and requires width/height. No contradictions.

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: first covers actions, second covers prerequisite and alternative. Every sentence earns its place, no 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?

Covers actions, results (list returns labels/titles/URLs/state, info returns size/position/title/focus/visibility), prerequisites, and alternatives. No output schema, but return info is described for list and info. Missing: what resize returns or success indication, but acceptable.

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?

Input schema covers all parameters with descriptions (100% coverage). Description adds value by emphasizing that width/height are required for resize action and explaining the logical pixel default, supplementing the schema's conditional requirements.

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 tool manages Tauri windows and lists three specific actions (list, info, resize) with distinct purposes. It differentiates from browser windows by directing to Chrome DevTools MCP.

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 states when to use this tool (Tauri apps only) and when not (browser windows: use Chrome DevTools MCP). Also mentions prerequisite (active driver_session).

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