rzil_list_sessions

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

With no annotations provided, the description carries the disclosure burden. It clearly indicates this is a read-only listing operation and discloses the output fields. However, it does not explicitly state that no sessions exist results in an empty list or describe any ordering or session ID format, though these are minor for a list operation.

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, focused sentence with no wasted words. It front-loads the action and resource, then lists the key returned fields, making it easy for an agent to parse quickly.

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, no-parameter listing tool, the description is largely complete: it names what is listed and the fields returned. It could be stronger by noting that it complements the rzil_init/rzil_destroy lifecycle and by distinguishing itself more explicitly from esil_list_sessions, but the core information an agent needs is present.

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 zero parameters and the schema description coverage is 100% with an empty properties object. Since there is nothing to document, the description correctly omits parameter guidance, matching the baseline for a no-parameter tool.

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 resource ('active persistent RzIL emulation sessions') and specifies the fields returned (session IDs, binary paths, creation times). It implicitly distinguishes from sibling tools like esil_list_sessions and debug_list_sessions through the 'RzIL' qualifier, though it does not explicitly name those alternatives.

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 states what the tool does but provides no guidance on when to use it versus alternatives such as esil_list_sessions or debug_list_sessions. There is no mention of prerequisites, such as initializing RzIL first, or exclusions for when this tool should not be used.

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