akb_recall

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

No annotations are provided, so the description must fully disclose behavior. It states it retrieves memories, implying read-only nature, but does not explicitly confirm no side effects, data mutability, or what happens if no memories exist. The behavioral info is minimal but not contradictory.

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 three clear, efficient sentences. The first sentence states core purpose, the second gives usage guidance, and the third explains filtering. No extraneous words, front-loaded with key information.

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 output schema, the description should explain what the tool returns (e.g., a list of memory objects). It does not specify return format or pagination details. With two parameters and no output schema, the description is adequate but missing return format, which is important for an agent.

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 50% (category has description, limit does not). The description adds meaning for category by explaining it filters for specific memory types, which supplements the enum values. However, it provides no additional info for the limit parameter, leaving its purpose solely to the schema's default and constraints.

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 retrieves persistent memories from previous sessions. It uses specific verb 'retrieve' and resource 'memories', and implies it is distinct from siblings like akb_remember by focusing on past data. However, it does not explicitly differentiate from akb_history or other retrieval 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 explicitly says to call this at the start of a session to recall work context. This provides clear usage timing. It does not mention when to avoid the tool or compare with alternatives like akb_history or akb_get, but the guidance is sufficient for typical use.

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