load_session

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

With no annotations provided, the description carries full burden. It describes the core behavior (loading recent session state) and timing (start of conversation), but doesn't disclose important behavioral traits like what happens if no session exists, whether this requires authentication, what data format is returned, or if there are rate limits. The description adds basic context but leaves significant gaps.

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 perfectly concise: two sentences that each earn their place. The first states what the tool does, the second states when to use it. No wasted words, well-structured, and front-loaded with the core purpose.

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 no annotations, no output schema, and a parameterless tool, the description provides adequate but incomplete context. It explains the purpose and timing well, but doesn't address what constitutes 'session state', what format it returns, error conditions, or how this integrates with sibling tools like 'save_session'. For a state management tool, more behavioral detail would be helpful.

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 0 parameters with 100% schema description coverage. The description appropriately doesn't waste space discussing parameters that don't exist. It focuses instead on the tool's purpose and usage context, which is the correct approach for a parameterless tool.

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: 'Load the most recent session state' specifies the verb (load) and resource (session state). It distinguishes from siblings like 'save_session' by focusing on retrieval rather than storage, but doesn't explicitly differentiate from other read operations like 'list_memories' or 'recall_memory'.

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 usage guidance: 'Call this at the start of a conversation to pick up where the last instance left off.' This tells the agent exactly when to use this tool (initialization/continuation scenarios) and implies it shouldn't be used mid-conversation for other purposes.

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