Get Session Info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety and side-effect profile. The description adds that the tool returns loaded contexts and variables, but it does not disclose return format, pagination, or any other behavioral traits. With annotations handling the core safety details, a score of 3 is appropriate.

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 sentence that is front-loaded with the action and resource, and contains no redundant or filler content. It is appropriately sized for a simple getter tool.

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 low complexity (one optional parameter, strong annotations, no output schema), the description covers the core functionality by stating what information is returned (loaded contexts and variables). However, it omits details about the complete return structure (e.g., additional session metadata), which would be more informative. Still, it is adequate for a simple read-only getter.

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 input schema has one parameter 'session_id' with a description, giving 100% schema description coverage. The description adds no extra parameter semantics (e.g., format, defaults, or behavior). Baseline 3 applies because the schema already documents the parameter adequately.

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 the specific verb 'Get' with the resource 'information about a session', and explicitly mentions 'loaded contexts and variables'. This clearly distinguishes it from sibling tools like rlm_get_variable and rlm_get_context_info, which target narrower scopes.

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 the tool should be used when a session-level overview is needed, mentioning loaded contexts and variables. However, it does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or prerequisites.

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