memo_chat_ask

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

Annotations declare readOnlyHint=true, but description mentions 'best-effort auto-capture side effects,' implying a write side effect, creating a contradiction. Description adds some behavioral info but at the cost of inconsistency.

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?

Description is two sentences, efficiently conveying purpose, usage, and key parameter roles. Minor room for improvement in structure but no wasted 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?

While it covers the main purpose and differentiates from sibling, it fails to document 5 of 8 parameters. Given output schema exists, return values are covered, but parameter documentation is incomplete for a tool with this many params.

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?

With 0% schema description coverage, description adds meaning for only 3 of 8 parameters (history, session_id, context). Other parameters (k, type, source, snippet_chars) remain undocumented, leaving gaps.

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?

Clearly states it answers conversational questions with optional history and context. Distinguishes from sibling memo_ask by specifying when to use it.

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 states 'Use instead of memo_ask when prior turns or explicit context should shape retrieval and synthesis,' providing clear guidance on when to choose this tool over its sibling.

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