goclaw_session_preview

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'preview' and 'recent messages,' which implies a read-only operation, but doesn't specify permissions, rate limits, whether it's safe or destructive, or what the output format looks like. This leaves significant gaps for an AI agent to understand the tool's behavior.

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, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'preview' entails (e.g., format, pagination, or error handling) or provide context for usage. For a tool with no structured behavioral data, more detail is needed to help an AI agent use it correctly.

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%, so the input schema already documents both parameters ('session_key' and 'limit') adequately. The description doesn't add any meaning beyond what the schema provides, such as explaining what a 'session key' represents or how 'recent' is defined. This meets the baseline for high schema coverage.

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's purpose with a specific verb ('preview') and resource ('recent messages in a chat session'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'goclaw_session_list' or 'goclaw_session_get', which might also involve session data retrieval.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'goclaw_session_list' and 'goclaw_session_get' available, there's no indication of when this preview tool is preferred or what distinguishes it from other session-related tools.

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