restart_firefox

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

The description explicitly mentions 'All current tabs will be closed,' which is a key behavioral trait. Annotations only provide readOnlyHint=false, so the description adds important context beyond that. However, it does not cover other potential side effects like download interruption or session loss.

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 concise with three sentences, front-loading the purpose. It avoids fluff but could be slightly more structured for clarity.

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?

The description covers the main behavioral impact (tabs closing) but does not address other potential state changes (e.g., ongoing downloads, extensions). Given moderate complexity with 6 parameters and no output schema, some gaps remain.

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%; each parameter has a description. The tool description does not add significant meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 'Restart Firefox with different configuration' and mentions changing binary path, environment variables, and other options. It also notes that all current tabs will be closed, providing a specific verb and resource with scope.

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 explicit guidance on when to use this tool versus alternatives. While the purpose implies restarting for configuration changes, there is no mention of alternative approaches or conditions for use.

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