firefox_parse_local_storage_tool

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

No annotations are provided, so the description carries the transparency burden. It adds useful behavioral context by naming the exact files parsed and the typical profile path, implying a read-only operation. However, it does not explicitly state that the tool only reads data and never modifies the profile, nor does it mention any prerequisites like profile availability or permission requirements.

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 two sentences: the first states exactly what the tool does, and the second provides a concrete example of a typical profile path. Every word earns its place—there is no redundancy or filler.

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 relatively simple parse tool with a full input schema and output schema, the description is nearly complete. It identifies the target resource and provides a path template. It could add a brief note about return format or that it only works on Firefox profiles, but the output schema covers return values and the description already gives sufficient context.

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 input schema provides 100% coverage of all four parameters with clear descriptions, so the baseline is 3. The tool description adds no additional meaning about parameters such as 'key', 'limit', or 'origin_key' beyond what the schema already states, and does not need to compensate.

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's purpose with a specific verb ('Parse') and resource ('Firefox local storage records'), and it explicitly names the two data sources ('webappsstore' and 'storage/default/ls'). This distinguishes it from sibling tools like history/cookies parsers and the Chromium local storage parser.

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?

The description implies usage by naming the resource and providing a typical profile path, which gives context for when to use it. However, it does not explicitly state when to prefer this tool over alternatives or mention any exclusions, leaving the agent to infer from the tool name and sibling list.

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