firefox_parse_cache_tool

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

With no annotations, the description must disclose behavioral traits. It only mentions parsing from a directory and provides a path example. It does not state whether the operation is read-only, whether the profile must be closed, whether it writes any temporary files, or any side effects. This is a significant gap for a tool that accesses browser storage.

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, front-loaded with the core purpose, and the path example is directly useful. Every sentence earns its place, with no redundant or filler content.

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?

The tool has five parameters and an output schema, but the description is minimal. Given the schema fully documents parameters and an output schema exists, the missing context is about the nature of cache records, potential size/performance implications, and the read-only nature. It is adequate but not complete for a storage-parsing tool.

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% and each parameter has a clear description (e.g., 'Optional exact request URL filter', 'Include cached body previews when the morgue file is present'). The description adds a typical profile path example which aids in understanding the profile_path parameter, but adds no new meaning beyond the schema's parameter descriptions.

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 it parses Firefox cache records from a specific path pattern, using the verb 'parse' with a specific resource. It differentiates from Chromium cache and other Firefox parse tools implicitly by naming Firefox and the cache directory, though it doesn't explicitly contrast with siblings like chromium_parse_cache_tool.

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 guidance is given on when to use this tool versus alternatives (e.g., chromium_parse_cache_tool or other Firefox parsers). The typical profile path offers some usage context, but there is no explicit 'when to use' or 'when not to use' direction.

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