chromium_decrypt_logins_tool

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

The description adds some behavioral context by explaining the two modes and providing a typical profile path. However, with no annotations, it does not fully disclose potential side effects, required privileges, or failure behavior beyond the word 'Attempt'. More detail about read-only nature or permission requirements would raise this score.

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 concise and well-structured, with a clear first sentence, an example path, and a bulleted list of modes. Every sentence contributes meaningful information without redundancy or unnecessary detail.

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?

Given the tool's complexity and the presence of an output schema, the description provides adequate context for selecting and using the tool. It covers the main usage modes and gives a concrete path example. It could briefly mention common failure scenarios, but the output schema handles return values, so this is a minor gap.

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 covers all parameters, and the description adds value by explaining how `master_key_b64` and `local_state_path` relate to the two decryption modes. The typical profile path example also helps clarify `profile_path`. The filtering parameters are self-explanatory and need no extra description.

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 uses a specific verb 'decrypt' and clearly identifies the resource as 'Chromium saved passwords from a browser profile'. It distinguishes the tool from siblings like chromium_parse_logins_tool, which likely only parses encrypted data, by emphasizing decryption.

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 implicitly indicates when to use this tool (to decrypt saved passwords) and outlines two distinct operating modes: Windows current-user context and offline with a master key. It does not explicitly name alternatives or state when not to use it, but the context is sufficient for an agent to make the choice.

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