Import logins from a CSV file

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds useful context that the browser itself maps column names and that only the standard layout is supported, but it never explains what the destructive aspect actually means here — whether existing saved logins are merged, duplicated, or overwritten — which is the one thing an agent most needs before calling it.

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 purpose is correctly front-loaded in the first clause, but the second sentence is largely internal trivia (resource:// module URI, class name, absence of prototype methods) that does not help an agent select or invoke the tool. Roughly half the text is noise against a one-parameter operation.

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?

For a destructive mutation with no output schema, the description says nothing about what happens to pre-existing logins, whether the import is idempotent, or what is returned on success/failure. The implementation trivia crowds out the behavioral information that would actually complete the picture.

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?

With a single parameter at 100% schema coverage, the schema already documents "Absolute path to the .csv file." The description adds only a constraint on the file's internal layout (url/username/password columns), which is mildly useful but does not extend the meaning of the `path` parameter itself. Baseline 3 applies.

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 states a specific verb and resource ("Import saved logins from a CSV") and even pins the exact export format, so the operation is unambiguous. It does not, however, distinguish itself from the near-identical sibling browser_import_logins_from_file (or browser_import_cookies_from_file), which an agent would have to disambiguate on its own.

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 implies usage through a constraint ("pass a file already in the standard url/username/password layout"), which tells the agent what input is acceptable. It gives no explicit when-to-use/when-not-to-use guidance and never routes the agent to the obvious alternative tool for the same job.

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