firefox_console

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

Adds substantial context beyond the annotations: required persistent read and debug permissions, a 15-minute or navigation-based expiry, the caveat that site instrumentation can be modified, worker exclusion, and a sensitive-data/untrusted-content warning. It does not explain why destructiveHint is true (presumably the clear action) or what read returns, but the disclosure is well above the annotation baseline.

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?

Five short sentences, front-loaded with the core purpose and followed by constraints and safety caveats. Dense and free of filler, though the telegraphic style leaves some terms (e.g. 'persistent read and debug access') unexplained.

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 five-parameter, four-action tool with no output schema and no parameter documentation, the description is too thin. It omits action semantics, which parameters apply to which action, and what read returns, so an agent cannot reliably invoke anything but the default capture flow.

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 0% across five parameters, so the description carries the full burden and largely fails it. It never explains tabId, frameId, maxResults, or the levels filter, and it does not describe what start/read/clear/stop do or which parameters apply to which action. Only the loose phrase 'console messages and errors' hints at the levels enum.

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?

States a specific verb and resource: 'Capture future document console messages and errors.' An agent can tell this is console capture rather than network or page reading. However, the tool is a four-action lifecycle tool (start/read/clear/stop) and the description only characterizes the capture phase, leaving the other actions unnamed.

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?

There is no explicit when-to-use guidance and no comparison to siblings like firefox_inspect or firefox_network, which an agent could easily confuse with console capture. The only routing-adjacent information is the prerequisite 'persistent read and debug access' and the expiry rule, which are behavioral rather than selection guidance.

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