resize_window

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

The description mentions clamping behavior and returns metadata, which adds some context beyond the schema. However, with no annotations, it does not fully disclose side effects (e.g., whether the window is also moved) or edge cases, leaving the agent to infer behavior.

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 concise with a front-loaded main sentence followed by parameter list and return note. Every sentence contributes to understanding, though the docstring format is slightly verbose for the parameter descriptions.

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 that there is an output schema and 6 parameters (2 required), the description covers all parameters and return value. It provides sufficient context for resizing, though deeper details about clamping logic (e.g., what happens when display_index is null) could improve completeness.

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 description provides brief parameter explanations (e.g., 'Target width in points') that add basic meaning beyond the schema. However, with 0% schema coverage, the descriptions are minimal and do not elaborate on default behaviors or parameter interactions (e.g., how app_name and window_id resolve).

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 resizes a macOS window and clamps it to the display, distinguishing it from siblings like move_window or center_window. The verb 'Resize' and resource 'macOS window' are specific and unambiguous.

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 implies usage for resizing windows with optional display clamping, but does not explicitly state when to use this tool over alternatives like move_window or tile_windows. No exclusions or when-not-to-use guidance is provided.

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