browser_install

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Install' but gives no indication of side effects, system modifications, required permissions, or reversibility. An agent has no idea what installing Chrome entails or what the outcome is.

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 brief (two words), which is concise, but it is under-specified rather than deliberately compact. There is no front-loading of key information because there is only one clause. Conciseness is not a virtue when it omits essential details.

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 installation tool with no annotations, no output schema, and no parameter elaboration, this description is grossly incomplete. It lacks information on behavior, effects, return values, and any prerequisites or usage constraints. An agent cannot safely or correctly invoke this tool based on the given definition.

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 schema provides a description for the single parameter 'deps' (Install system deps), giving 100% coverage. The tool description adds no additional meaning beyond that. Per the baseline rule, a score of 3 is appropriate since the schema covers the parameter adequately.

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 specific verb and resource: 'Install Chrome.' It is clear what the tool does, but it doesn't differentiate from siblings. However, none of the sibling tools are install-related, so it stands out naturally. The purpose is unambiguous but lacks any additional scoping.

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 or when not to. There is no mention of prerequisites, alternatives, or context. The description is a single imperative phrase with no supporting conditions.

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