firefox_parse_logins_tool

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

No annotations are provided, and the description does not disclose behavioral traits such as whether it is read-only, whether it requires specific permissions, or that it does not decrypt passwords. Given the existence of a decrypt sibling, this omission is significant. The description adds little beyond the schema.

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?

Two sentences: the first states the function, the second provides a useful path example. No redundancy, front-loaded, and every sentence earns its place.

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?

Output schema and parameter schema are complete, covering return and parameter details. However, the description does not clarify the scope of 'metadata' (e.g., excludes decrypted passwords) or differentiate from firefox_decrypt_logins_tool. This is a notable completeness gap for tool selection.

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 description coverage is 100%, so the parameters are already documented. The description adds a typical profile path example for profile_path, which is helpful but does not clarify limit or hostname semantics beyond the schema. This meets the baseline for high schema coverage.

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?

Description clearly states 'Parse Firefox saved-login metadata from logins.json' – a specific verb+resource. The sibling 'firefox_decrypt_logins_tool' reinforces that this tool handles metadata, making the purpose distinct even if not explicitly contrasted.

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?

Provides a typical Firefox profile path as practical usage context, implying when to use the tool (when you have a profile path). However, it gives no explicit guidance on alternatives or exclusions, such as not using this tool when decrypted passwords are needed.

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