chromium_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 full burden of behavioral disclosure. The description only says 'Parse' and gives a path example; it does not state whether the tool is read-only, whether it modifies the profile, what side effects or limitations exist, or what the output format is. It lacks transparency about the operational behavior beyond the basic action.

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 with no fluff. It front-loads the primary purpose and then provides a helpful example. Every word earns its place, making it highly efficient and well-structured.

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 is a medium-complexity parser with 5 parameters, an output schema, and many sibling tools. The description adequately covers the core purpose and provides a useful path example, but lacks usage guidance and behavioral context. Given the output schema covers return values, the overall completeness is adequate but has clear gaps in usage and transparency.

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 schema already provides 100% description coverage for all 5 parameters, so the baseline is 3. The description adds meaningful value by giving a concrete example path for the required profile_path parameter, which aids in correctly selecting the path. This extra context justifies a slight increase above baseline.

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 action ('Parse') and the specific resource ('Chromium Local Storage records from a browser profile'). The verb+resource combination is specific and unambiguous, distinguishing it from sibling tools that parse history, cookies, etc., and from the related session_storage and indexeddb tools.

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 gives no explicit guidance on when to use this tool versus alternatives. It only provides a typical profile path, which is more about parameter context than usage decisions. There is no mention of exclusions, alternatives, or conditions under which this tool should be preferred.

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