chrome_type

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that typing uses Chrome's real input and that perCharacter sends individual keydown events, but it does not mention tab activation, background behavior, return values, or what happens when no selector/uid is provided.

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 filler: the first front-loads the action and target, the second gives focused parameter guidance. Every sentence 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 an 11-parameter tool with no annotations and no output schema, the description is too sparse. It omits targeting semantics, snapshot behavior, operational side effects, and return expectations, leaving an agent with significant gaps.

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 only 45%, so the description should compensate for the remaining parameters. It adds meaning for uid, selector, and perCharacter, but leaves text, pressEnter, maxElements, includeSnapshot, and several targeting parameters unexplained.

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 states a clear action: focus an optional snapshot uid or CSS selector, then type via Chrome's real input. It identifies the resource and core behavior, though it does not explicitly distinguish itself from sibling tools like chrome_fill or chrome_key.

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 guidance is given for when to use this tool versus alternatives. The only conditional advice, 'Set perCharacter=true for editors needing individual keydown events,' addresses a parameter setting rather than tool selection.

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