nex_proxy_list

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

Annotations already declare readOnlyHint=true, and the description adds valuable context: credentials are never returned, and the scope is the active NexBrowser workspace. This goes beyond the annotation by disclosing a privacy-relevant behavior, though it does not mention pagination or result format.

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 two concise sentences, front-loaded with the action and purpose. Every sentence earns its place, and there is no redundant or vague wording.

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 conveys the main purpose and an important caveat (credentials not returned), but with no output schema and four undocumented optional parameters, it lacks detail about return shape and how parameters influence results. It is adequate for a simple list tool but leaves meaningful gaps.

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% and the description does not explain any of the four parameters (page, size, source, keyword). The parameter names give some intuitive hint, but the description adds no explicit meaning about filtering, pagination, or how these parameters affect the list result.

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 ('List') and a specific resource ('proxy resources available in the active NexBrowser workspace'), clearly distinguishing this tool from sibling browser tools like nex_browser_list or nex_browser_group_list. It also states the intended outcome: selecting a proxyId for window creation or binding.

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: it is meant to be used before creating or binding a window so a proxyId can be chosen. It does not explicitly mention alternatives or when not to use it, but the use case is sufficiently clear given the sibling tool names.

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