memo_rename

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

Annotations already indicate destructiveHint=true, and description explicitly states 'Destructive metadata edit.' It adds context about targeting the most recent local save when id is omitted, and confirms title-only modification.

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?

Two short paragraphs, first sentence clearly states purpose. Every sentence adds value with no redundancy. Front-loaded with core action.

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 the existence of an output schema and annotations covering destructive nature, the description fully covers purpose, usage guidelines, and behavioral nuances. No gaps.

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?

Although schema description coverage is 0%, the description explains the id parameter behavior (pass for specific memory, omit after save) and mentions title implicitly. This adds meaningful context 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?

The description states 'Rename one memory title without changing its body or tags.' It clearly identifies the verb (rename), resource (memory title), and scope (no changes to body/tags). It distinguishes from sibling memo_update which edits content, type, or tags.

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 specifies when to use: after memo_save or memo_search when content is correct but title is wrong. Provides guidance on id parameter: pass id for specific memory, omit only after save. Advises using memo_update for editing content, type, or tags.

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