session_manager

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

No annotations provided, so description carries the full burden. It only mentions 'isolated sessions' and 'working directory' but omits details like side effects, authentication needs, or rate limits. The actions from the schema are not elaborated upon in the description.

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?

Two concise sentences, front-loaded with clear subject and verb. Every word serves a purpose. No repetition or fluff.

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 no output schema and multiple actions, the description should provide more context about return values and action-specific behavior. It lacks completeness for a tool with 3 parameters and 5 actions. More details are needed for effective use.

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 100% for all 3 parameters, so the bar is higher. The description adds no additional meaning beyond the schema; it only restates the overall purpose. Thus, it meets the baseline but does not enhance parameter understanding.

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 manages isolated sessions for Rovodev CLI operations, specifying sessions have their own working directory and maintain context. This distinguishes it from sibling tools which are unrelated to session management.

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 implies usage for session management but does not explicitly state when to use vs alternatives or provide exclusions. However, it lists the possible actions (create, destroy, list, get, cleanup) which offer some guidance. Siblings are clearly different, so context is clear but not exhaustive.

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