jambavan_memory_recall

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

Discloses that ordinary recall does not start MemPalace and that mempalace provider is read-only. However, lacks details on side effects, authentication needs, or what 'active' means. No annotations present, so description carries full burden.

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?

Extremely concise: two sentences efficiently state purpose, key parameter options, and a behavioral caveat. No unnecessary words.

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?

Explains what the tool does and parameter usage, but does not describe return format or output structure. For a recall tool with no output schema, this is a notable gap.

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 covers all four parameters with descriptions. Description adds value by explaining default limit, newest-first ordering, and provider behavior (e.g., separate sections), going beyond the 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?

Description clearly states the action (recall), resource (Jambavan memories), ordering (newest first), and default limit. Differentiates from sibling tools like jambavan_memory_get or jambavan_memory_store by focusing on listing.

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?

Provides guidance on using provider parameter (e.g., 'Set provider=mempalace for an explicit read-only drawer listing'), but does not explicitly compare to alternative tools or state when to use this tool over siblings.

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