nex_account_list

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

Beyond the readOnlyHint annotation, the description adds a behavioral guarantee that 'Secrets are never returned.' It also clarifies the catalog vs. open-window vault distinction, which is a behavioral scoping. There is no contradiction with the annotation.

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?

Three sentences, each serving a distinct purpose: stating the primary action, routing away from a sibling, and reassuring about secrets. There is no fluff, and the key disambiguation is placed early.

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 is sufficient for basic usage (calling with no parameters) and offers strong usage context, but it omits any explanation of how the parameters affect the result. Since there is no output schema, an agent cannot infer the return format beyond 'list of accounts with IDs.' This is a moderate gap for a tool with pagination and filtering options.

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?

The description contains zero information about any of the four parameters (page, size, teamId, keyword). Since schema coverage is 0%, the description must compensate for the missing parametric guidance, but it does not. An agent cannot know how to filter or paginate from this text.

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 starts with a clear verb and resource: 'List platform accounts in the workspace catalog.' It also states the intended usage ('so an accountId can be selected for window creation or later vault fill') and explicitly disambiguates from the sibling nex_browser_accounts, making its purpose unmistakable.

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 explicit when-to-use guidance by contrasting with nex_browser_accounts: 'This is not the open-window vault; use nex_browser_accounts after a window is running.' This tells the agent exactly when to choose this tool over the alternative.

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