restart_firefox

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

Annotations set readOnlyHint=false, consistent with a mutation. The description adds important behavioral context: 'All current tabs will be closed.' It also mentions the ability to change binary path and environment variables, which are key side effects. No contradictions.

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 three sentences with no redundancy. Each sentence provides distinct information: the action, the configurable items, and the consequence (tab closure). It is efficient and front-loaded with the core purpose.

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 6 parameters fully described in the schema and no output schema, the description covers key context: closing tabs. However, it omits prerequisite info like MOZ_REMOTE_ALLOW_SYSTEM_ACCESS=1 for prefs, which appears only in parameter schema. Still sufficient for most use cases.

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 100%, so the baseline is 3. The description summarizes parameters ('binary path, environment variables, and other options') but adds no new information beyond the schema's individual field descriptions. It does not enhance understanding of parameter relationships or constraints.

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 action (Restart) and the resource (Firefox) with the purpose of changing configuration. It distinguishes from sibling tools like navigate_page or close_page, which do not restart the browser. The mention of 'All current tabs will be closed' provides a specific behavioral outcome.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implicitly suggests use for restarting with different config, but lacks 'when not to use' or comparisons to siblings. The uniqueness of the tool among siblings makes the purpose clear, but guidelines are minimal.

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