session_state

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

Annotations indicate a safe read-only operation. The description adds valuable behavioral context beyond annotations: that wall-timeout or session_reset empties the loaded frames but leaves stored_handles, and that loaded frames include frame_handle. This clarifies the state 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 a single, dense sentence that front-loads the core purpose and adds essential lifecycle context. No wasted words; every phrase earns its place.

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?

The description sufficiently covers what the tool returns (loaded frames, variables, stored_handles) and the persistence behavior. It does not describe the exact return format, but for a zero-parameter state inspection tool with no output schema, this is adequate and not incomplete.

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?

With zero parameters, the baseline is 4. The description adds no parameter details, but none are needed.

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 explains what the tool returns (kernel state: loaded frames, user variables, stored_handles), but lacks an explicit verb like 'List' or 'Get'. It implicitly distinguishes from siblings by referencing session_reset, which is related.

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 is clear: this tool inspects the current session state. It doesn't explicitly state when to use it versus alternatives, but the purpose strongly implies it. No exclusions are mentioned, but the mention of session_reset provides lifecycle context.

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