agentmem

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

No annotations are provided, so the description carries the full burden. It discloses that the tool loads the 'most recent' session state, implying it's a read-only operation that retrieves data without modification. However, it doesn't address potential behaviors like error handling if no session exists, authentication needs, or rate limits, leaving gaps in transparency for a tool with no annotation support.

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 two sentences, front-loaded with the core purpose and followed by usage guidance. Every word earns its place, with no redundancy or fluff, making it highly efficient and easy to parse.

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 has no parameters, no annotations, and no output schema, the description is minimally complete. It explains what the tool does and when to use it, but lacks details on return values (e.g., what 'session state' includes) or error scenarios, which could be important for an agent to handle this tool effectively in a memory-heavy context with siblings like 'save_session'.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, focusing instead on usage context. This meets the baseline for tools with no parameters, as it doesn't introduce unnecessary complexity.

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.' It specifies the verb ('load') and resource ('session state'), and while it doesn't explicitly differentiate from siblings, it implies a contrast with 'save_session' as a complementary operation. However, it doesn't detail what 'session state' entails compared to other memory-related tools.

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 clearly indicates when to use the tool (at conversation start) and its intended context (continuity from previous sessions), with an implied alternative being not to call it if starting fresh.

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