camofox_set_viewport

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

Discloses that it triggers a real layout reflow and uses Playwright's setViewportSize. No annotations exist, so description carries full burden; could mention side effects (e.g., scroll reset) or permissions.

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 efficient sentences: front-loaded with purpose, then technical implementation detail. No wasted words.

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?

No output schema, no annotations, and parameter semantics are absent. Missing return value, error conditions, prerequisites (e.g., valid tabId). Incomplete for a tool with 4 required params.

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?

Schema coverage is 0%, but description provides no details on parameters (width, height, tabId, userId). Agent gets only parameter names from schema, no units or 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?

Clearly states the tool sets viewport size via Playwright's setViewportSize, triggering real layout reflow. Distinguishes from sibling tools like navigate, click, etc., and contrasts with window.resizeTo.

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 recommends usage for responsive testing and notes that window.resizeTo is ineffective on non-popup windows. However, lacks explicit when-not-to-use or alternative tools.

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