openclaw_sessions_preview

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

Explicitly declares 'Read-only', a key behavioral trait. Also mentions internal wrapping of 'sessions.preview'. With no annotations, the description provides essential transparency about safety and data access.

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?

Three sentences, each carrying weight: main purpose, read-only nature, parameter guidance. No fluff, information is front-loaded.

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?

Adequately covers tool purpose, return content, and parameter details. Lacks specifics about output format or message limit, but for a simple preview tool it's sufficient.

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 coverage is 100%, but description adds value by explaining that keys are 'full session keys' from openclaw_sessions_list with an example, and clarifies the instance parameter's fallback behavior. Goes beyond bare schema.

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?

Clearly states verb 'Preview', resource 'sessions', and what it returns ('recent messages, status, and metadata'). Distinguishes from sibling tools like openclaw_sessions_subscribe by noting 'without subscribing', and references openclaw_sessions_list for key format.

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?

Implies usage when you need session data without subscribing, and instructs to obtain keys from openclaw_sessions_list. Could be more explicit about when not to use alternatives, but guidance is clear.

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