velixar_session_recall

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

No annotations provided, so description bears full burden. Discloses that it recalls memories with filtering and ordering options, but does not describe behavior on missing sessions, rate limits, or authorization needs. Adequate but could be more detailed.

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?

Three sentences, each serving a distinct purpose: purpose, usage context, and parameter specifics. No redundant or unnecessary wording. Highly efficient.

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 7 optional parameters and no output schema, the description covers main use cases and links to sibling tool (session_resume). Could mention return format or default behavior, but sufficiently complete for a recall tool.

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 100% (7 parameters described), so baseline is 3. Description adds value by explaining usage context (e.g., chunk_id from session_resume manifest, order='chronological' for narrative reconstruction) beyond schema descriptions.

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 'Recall memories from a previous session' with specific resources (session ID, date, topic) and a distinct verb. Differentiates from siblings like velixar_search (general search) and velixar_session_save/resume.

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?

Explicitly says 'Use when resuming work to restore prior context' and provides parameter-specific guidance (chunk_id for drill-down, order='chronological' for full narrative). Does not explicitly exclude alternatives but provides sufficient context.

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