window

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Manage browser windows and tabs,' which gives no information about mutability, side effects, or dependencies. Important details like whether actions affect the current session, require an active browser, or have irreversible effects are omitted.

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 concise at 6 words, but this brevity sacrifices informativeness. It is front-loaded with the verb, but the lack of detail makes it under-specified. Effective conciseness would retain clarity while providing necessary context; here it fails to do so.

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 the tool's complexity (multiple action types, optional handle parameter) and the absence of an output schema, the description is severely incomplete. It does not cover return values, edge cases, or prerequisites. An agent would struggle to use it correctly without exploring the schema or external documentation.

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%, meaning the description does not explain the parameters. The two parameters (action and handle) are not defined in the description. The action enum values are listed in the schema but not explained semantically. The handle parameter's purpose is entirely unclear without additional context.

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 'Manage browser windows and tabs' clearly identifies the verb (manage) and resource (browser windows and tabs). It conveys the general purpose, though it does not differentiate from sibling tools like navigate or open_url, which also manage browser state. The action enum in the schema provides specificity, but the description alone is moderately clear.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like navigate or start_browser. There is no mention of prerequisites, conditions, or exclusions. The agent must infer usage from the schema or context.

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