get_firefox_info

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

The description discloses that the tool returns specific configuration information (binary path, env vars, output file location) with no mention of side effects; since no annotations are provided, the description adequately covers the read-only nature.

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?

Single sentence of 18 words, front-loaded with purpose, no extraneous information.

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 a zero-parameter tool with no output schema, the description lists key return fields (binary path, env vars, output file location), making it sufficiently informative; could be slightly improved by noting that the info is a snapshot at call time.

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 tool has no parameters, and the description adds value by detailing what information is retrieved, surpassing the schema which is empty.

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 specifies 'Get information about the current Firefox instance configuration' with examples (binary path, environment variables, output file location), clearly distinguishing it from sibling tools that perform actions like clicking or filling.

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?

Implied usage is for retrieving configuration details, but no explicit guidance on when to use this tool versus alternatives like 'get_firefox_output' or other informational tools is provided.

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