session_resize

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

There are no annotations, so the description carries the disclosure burden. It mentions that a prior session_start is required and describes the action, but it does not disclose side effects on the current page/session, error conditions, or whether the resize persists after navigation.

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 extremely terse, front-loaded, and every sentence contributes information: what it does, when it is relevant, and a prerequisite. There is no filler or redundancy.

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?

The core purpose and session_start prerequisite are present, and an output schema exists. However, with no annotation and no parameter documentation, the agent still cannot correctly infer the meaning and constraints of max_chars, nor does it know the exact behavioral contract beyond 'resize viewport'.

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 description coverage is 0% and the description does not mention any parameter. Width and height are semantically inferred from 'viewport resize', but max_chars is completely unexplained; the description fails to compensate for the missing schema documentation.

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 clearly states an action ('resize viewport'), identifies the resource ('active tab'), and gives the context ('responsive sites'). This distinguishes it from session navigation, clicking, and other session tools.

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?

The description explicitly says 'Requires session_start', giving an important prerequisite. It does not explicitly name alternatives or say when not to use it, but among sibling tools there is no other viewport-resize operation, so the guidance is clear enough.

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