tool_set_window_size

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

With no annotations, the description must disclose behavioral traits. It only states the action but does not mention whether the size applies to the current window, if it is persistent, or if there are constraints (e.g., minimum/maximum sizes). A simple 'set' operation lacks details about side effects or prerequisites.

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 a single sentence, which is concise. However, it is too brief and sacrifices necessary detail; a slightly longer description could improve clarity without being verbose.

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 (2 required integer parameters, no output schema, no annotations), the description fails to provide enough context. It does not explain what 'set' implies (e.g., resizing the browser viewport) or how it relates to other window size tools. The agent lacks information to use it correctly.

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 input schema has 0% description coverage, meaning no parameter descriptions. The description does not compensate by explaining that 'width' and 'height' refer to pixel dimensions, valid ranges, or behavior if values are out of bounds. The agent must infer from parameter names alone.

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 'Set the browser window size' uses a specific verb and resource, clearly indicating the action. It distinguishes from sibling tools like 'tool_get_window_size' or 'tool_maximize_window' by its focus on setting dimensions rather than reading or adjusting to extremes.

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?

No guidance is provided on when to use this tool versus alternatives like 'tool_maximize_window' or 'tool_fullscreen_window'. The description lacks context such as setting a specific size for layout testing or ensuring consistency across sessions.

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