memo_save_text

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

Annotations (readOnlyHint=false) already indicate write operation. Description adds that it 'returns the saved memory id' and title is optional, providing useful behavioral context beyond annotations.

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?

Concise with front-loaded purpose 'Save a memory from text.' followed by clear details. Every sentence adds value with no redundancy.

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?

With 2 params, high schema coverage, and presence of output schema, description explains purpose, return value, and parameter behavior adequately. Could mention that it's a simple save without conflict handling, but that is already implied by comparison with memo_save.

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%, so baseline is 3. Description adds that title is optional and auto-generated from first line, but this info is also in the schema description. No significant additional meaning beyond 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 'Save a memory from text' and 'Persists one plain note from text and returns the saved memory id.' It distinguishes from siblings by explicitly mentioning memo_save for more options and memo_idle_capture for transcripts.

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 when to use this tool: 'Use for quick client-agnostic saves when you already have the exact content to remember.' Also provides alternatives: 'Prefer memo_save when you need tags... Prefer memo_idle_capture for transcript-derived session insights.'

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