chrome_type

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

No annotations are provided, so the description must cover behavioral traits. It discloses setting a value and firing an input event, but omits details like whether the element must be visible, if it clears existing values, or error handling. The truncation suggests additional information is missing.

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 very short, but truncated. It lacks completeness and does not earn its place as it is too brief to be fully helpful. A concise description that covers key points would score higher.

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 (browser automation), the description is insufficient. There is no output schema, no annotations, and no error or behavior details. Essential context like element waiting, error handling, and interaction with page state is missing.

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?

The input schema has no properties (0 parameters), so baseline is 4 per rules. The description implies parameters like CSS selector and value, but since none are defined, it does not add meaning beyond the schema. The inconsistency between implied parameters and empty schema is noted but does not lower the score under the given rubric.

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 the tool sets the value of an input/textarea matching a CSS selector in the current Chrome tab and fires an input event. It specifies the verb and resource, but does not differentiate from sibling tools like chrome_fill_form, which may have overlapping functionality.

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 provided on when to use this tool versus alternatives such as chrome_fill_form or web_type. There are no prerequisites, contexts, or exclusions mentioned.

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