pilot_resize

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

Describes the return value and that any valid pixel dimensions are accepted. Lacks mention of potential side effects (e.g., resize affecting current tab only, no zoom change), but sufficient for a simple action.

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?

Brief, well-structured description with separate sections for purpose, usage, parameters, return, and errors. No unnecessary 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?

Covers all necessary aspects: purpose, when to use, parameters with examples, return value, error handling, and sibling differentiation. Complete for this simple tool.

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?

Adds example values for desktop and mobile beyond the schema's description, clarifying units and providing context for typical use.

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 action (set viewport size), resource (browser viewport), and simulation goal. Distinguishes from sibling pilot_responsive by noting the multi-viewport screenshot alternative.

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 states when to use (responsive testing, simulating screen sizes) and provides an alternative tool for multi-viewport screenshots.

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