restart_firefox

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

The description discloses that all current tabs will be closed, which is a key behavioral consequence. However, it does not mention other effects like session saving, unsaved data loss, or the requirement for MOZ_REMOTE_ALLOW_SYSTEM_ACCESS=1 for prefs, which is only in the schema. With no annotations, the description should provide more context.

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 concise, consisting of two clear sentences with no extraneous information. It front-loads the main purpose and immediately states the critical consequence, making it easy to parse.

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 complexity (6 parameters, nested objects, no output schema), the description is moderately complete. It explains the core action and a key effect (tabs closed), but omits details like return value, warning about unsaved state, and prerequisite environment variable for prefs. More context would be helpful for a restart operation.

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 coverage is 100% with parameter descriptions already present. The description adds only a high-level summary (binary path, environment variables, options) without deepening understanding. It does not introduce new semantics or clarifications beyond the schema.

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 restarts Firefox with changed configuration, specifying verb 'restart' and resource 'Firefox'. This distinguishes it from sibling tools like close_page, navigate_page, etc., which are single-page actions.

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 is provided on when to use restart_firefox versus alternatives (e.g., after installing an extension, or for resetting state). There are no usage conditions, prerequisites, or scenarios mentioned.

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