chromium_parse_logins_tool

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

With no annotations, the description carries the full burden. It explicitly states the tool 'Reads' the database and returns metadata without decrypting passwords, implying a read-only, non-destructive behavior. However, it does not detail any potential side effects or permission requirements beyond the path context.

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 front-loaded with purpose, using four short sentences. The note about the Local State file is slightly tangential for a non-decrypting tool but does not detract significantly; it could potentially confuse but is placed clearly in the context of decryption.

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 description explains the tool's scope (metadata only), the database it reads, and typical profile paths. It distinguishes from decrypt_logins and other parsers. An output schema exists, so return values are covered, and the description is sufficient for a read-only parser.

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 all parameters have descriptions in the schema. The tool description itself adds minimal parameter-specific value, though the typical profile path example aids understanding of the profile_path parameter. This aligns with the baseline of 3.

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 parses Chromium saved-login metadata from a browser profile, specifically reading the Login Data database and returning metadata without decrypting passwords. This distinguishes it from the sibling chromium_decrypt_logins_tool and other parse 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 provides clear context by specifying it reads metadata without decrypting passwords, which implicitly indicates when to use this tool (for metadata) versus a decryption tool. It also gives a typical profile path and mentions Windows Local State for decryption, but does not explicitly name alternatives.

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