nex_browser_accounts

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

The readOnlyHint annotation is already present, and the description reinforces safety by adding that usernames are masked and secrets are never returned. This adds valuable behavioral context about data handling beyond the annotation, though it doesn't discuss rate limits or side effects.

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, zero waste, front-loaded with the key capability. Perfectly scannable.

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 simple list operation with one parameter, this is complete. The browser and plugin context are clear. The description tells the agent everything needed to understand input, output, and follow-up actions.

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 0%, but the tool only has one parameter (windowId) which is self-explanatory as a window identifier. The description doesn't need to add much. The parameter likely means 'which window', and the description focuses on the valuable semantics of the result set.

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 lists autofill-capable credentials in NexBrowser vault plugin, including bound platform accounts and user-saved passwords. It distinguishes itself as a read/list operation from the sibling tools like nex_browser_fill_account.

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?

Explicitly states when to use this tool (to list credentials) and directly references the alternative/next step: call nex_browser_fill_account with an accountId from this result. This is excellent usage guidance.

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