bob_list_sessions

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

No annotations are provided, so the description must convey behavioral details. It only states the basic listing action and scope, but omits any information about output format, sorting, default behavior when the optional workspace parameter is omitted, or whether it is a read-only operation. This is a significant gap for a tool with no annotation support.

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, clear sentence with no redundant words. It is perfectly sized for a straightforward list operation and front-loads the core action.

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 tool with one optional parameter, the description is mostly adequate. However, it does not clarify the default for 'current' when the workspace parameter is omitted, which is a gap given the schema marks it optional. Since there is no output schema, a brief mention of what is returned would improve completeness.

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 schema provides full coverage for the single 'workspace' parameter with a clear description. The tool description adds no extra meaning beyond the schema, simply restating the workspace scope. With 100% schema coverage, baseline 3 is appropriate.

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' with a clear resource 'Bob Shell sessions' and scope 'current project workspace.' It clearly distinguishes this from the sibling tools (prompt, version, resume) by explicitly naming the action of listing sessions.

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 context of listing sessions is clear and logically implies use before resuming or prompting. There are no explicit exclusions, but the tool's purpose is self-evident given the sibling names. No alternatives are named, but none are needed for a listing operation.

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