resize

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

The description adds genuine behavioral context beyond the annotations: it discloses that the size persists for the session and that it can alter page rendering due to responsive layout. This complements the idempotentHint=true and readOnlyHint=false annotations without contradicting them.

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 sentences with no waste: the core action is front-loaded, and the behavioral implications (persistence, rendering impact) follow. Every clause earns its place.

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?

For a simple two-parameter tool with an output schema and safety-related annotations, the description covers the essentials well. Minor gaps remain—units are unspecified and the relationship to the overlapping 'emulate' sibling is unaddressed—but nothing critical blocks correct invocation.

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 coverage, the description carries the burden, and the phrase 'to width x height' does connect the two integer parameters to their role as viewport dimensions. However, it adds no units, bounds, or constraints, leaving the semantics only minimally richer than the raw schema.

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 uses a specific verb and resource ('Resize the browser viewport to width x height'), making the tool's function immediately clear. It is unambiguous, though it doesn't explicitly differentiate from the sibling 'emulate' tool, which could also affect viewport size.

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 when-to-use, when-not-to-use, or alternative guidance is provided. The persistence note ('The size persists for the session') implies a usage context, but there is no explicit routing relative to overlapping siblings like 'emulate', leaving the agent to infer when this tool is preferred.

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