Set Browser Viewport

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

Beyond annotations, description warns of side effects like reflow, lazy loading, analytics, and network requests. This adds valuable transparency not captured by annotations.

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?

Three sentences cover use case, preconditions, and side effects efficiently. Could be more direct but no wasted content.

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 presence of output schema and annotations, description provides sufficient context for its two-parameter tool: when to use, preconditions, and behavioral impact.

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?

With 0% schema description coverage, description only says 'positive width and height', not explaining units or semantics (e.g., pixels). Minimal added value beyond the schema's constraints.

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 the tool is for setting viewport dimensions when responsive breakpoints matter, which is clear and distinguishes from navigation or screenshot tools. However, it could be more direct like 'Sets browser viewport width and height.'

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?

Provides context for when to use ('full-profile reproduction depending on responsive breakpoints') and preconditions, but lacks explicit when-not-to-use or alternatives among sibling tools.

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