Read the about:support troubleshooting snapshot

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context about the module and the returned sections, but it does not disclose privacy implications, output size, or the exact default subset.

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 front-loaded with the purpose and remains fairly short. The internal module path and Troubleshoot.snapshot() detail are somewhat implementation-heavy for an agent choosing and calling the tool, but they do not obscure the main point.

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 one-parameter read-only diagnostic tool with full schema coverage and no output schema, the description is nearly complete: it names the snapshot source and many returned sections. It could still say more about the default subset and whether the snapshot contains sensitive or large data.

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%, so the schema already documents the single optional sections parameter. The description adds value by naming example top-level sections and stating that sections narrows the output, though the list is introduced with 'including' and is not exhaustive.

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 specific resource and verb: it returns the diagnostic snapshot shown by about:support. It is distinguishable from most browser tools by the about:support and Troubleshoot.snapshot() references, though it does not explicitly contrast itself with nearby diagnostic siblings such as browser_selfcheck or browser_profile_info.

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?

Usage is implied by the diagnostic/troubleshooting nature of the tool, and the description says to use sections to narrow the output. However, it gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance.

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