get_command_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists commands with descriptions, but doesn't reveal any behavioral traits such as whether the output is paginated, sorted, or filtered; if there are rate limits; or what authentication might be required. This leaves significant gaps in understanding how the tool behaves in practice.

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 a single, efficient sentence that directly states what the tool does without any unnecessary words. It's front-loaded with the core action ('List all available Selenix commands') and includes a helpful parenthetical example ('click, type, open, etc.') to clarify scope, making it highly concise and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It explains the basic purpose but lacks behavioral context (e.g., output format, limitations) and usage guidelines relative to siblings. For a read-only listing tool, this is minimally viable but could be more informative about what the agent should expect.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics, so it appropriately focuses on the tool's purpose. A baseline score of 4 is given since no parameters are present, and the description doesn't attempt to explain nonexistent inputs.

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's purpose with a specific verb ('List') and resource ('all available Selenix commands'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_command_info' or 'get_selected_command_info', which might provide more targeted information about specific commands rather than a comprehensive list.

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 no guidance on when to use this tool versus alternatives. It doesn't mention scenarios where this tool is preferred over siblings like 'get_command_info' (for details on a specific command) or 'get_active_suite' (for commands in a test suite), nor does it specify prerequisites or exclusions for usage.

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