resize_window

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

Annotations already indicate mutating (readOnlyHint false) and non-destructive behavior. The description adds that it returns updated geometry JSON or an error, but does not disclose potential failure modes or permission requirements beyond what is in the schema.

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 short and to the point, with clear Args and Returns sections. No unnecessary verbiage, but the Returns could be inferred from the output schema.

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 simplicity (resizing a window) and the presence of detailed schema descriptions for parameters, the description is adequate but not thorough. It could mention how to identify the window (by title or handle) and that it uses case-insensitive substring matching.

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 tool description only mentions 'target window plus new width, height' without detailing the multiple ways to specify the window (title, handle, display) or their relationships. With 0% schema description coverage, the description fails to add meaningful context beyond the schema.

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 'Resize a window to a new width and height,' which is a specific verb and resource. It distinguishes from sibling tools like move_window (position) and hide_window (visibility).

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 does not provide guidance on when to use this tool versus alternatives, nor does it mention prerequisites like having a window handle or title from list_windows. Usage is implied but not explicit.

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