Create Session

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

The description adds context about isolation ('isolated', 'independent processing contexts') but does not disclose whether sessions are persistent, require cleanup, or return a handle. Annotations are neutral (all false), so the description carries the burden. It gives some insight but not a full picture of session lifecycle.

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 concise: three short sentences, with the main action front-loaded. Each sentence serves a purpose: stating the action, specifying when to use, and clarifying that the default is usually sufficient. No wasted words.

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 has no parameters and no output schema, the description adequately covers what it does and when to use it. It misses explaining the return value or session identifier, but for a simple create operation, the description is nearly complete. Sibling tools imply a session model, but the description doesn't elaborate.

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 schema coverage is 100% vacuously. Per the rubric, 0 parameters yields a baseline of 4. The description correctly does not add parameter info since none exist.

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 action: 'Create a new isolated RLM session.' The verb 'create' and resource 'RLM session' are specific. The qualifier 'isolated' and reference to 'multiple independent processing contexts' distinguishes it from other session-related tools like rlm_clear_session.

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 guidance: 'Use this when you need multiple independent processing contexts.' It also includes a clear exclusion: 'Most use cases can use the default session.' This tells the agent when not to use the tool and implies an alternative (the default session).

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