memo_set

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

With no annotations, the description carries full burden. It discloses that the tool returns a short ID for retrieval, which is useful behavioral information. However, it does not mention side effects, persistence, overwriting, or any prerequisites, leaving the agent with only a minimal understanding of the operation's behavior.

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 sentences with no filler. The first sentence uses an imperative verb ('Save') and clearly states the purpose; the second explains the return value. Every word earns its place, making it highly concise and well-structured.

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?

The description explains the tool's purpose and return value, and the schema covers all parameters. Given the relative simplicity of the operation, it is reasonably complete. Missing are details about side effects or edge cases, but the essential context for using the tool is present.

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?

The input schema already describes all six parameters with 100% coverage, so the baseline is 3. The description does not add any additional meaning to the parameters, but this is acceptable because the schema already provides the necessary details.

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 clearly states the tool's action: 'Save the current conversation context' with a specific verb and resource. It distinguishes itself from siblings (memo_get, memo_list, memo_delete) by focusing on creation, and the context 'handoff to another session or agent' clarifies its unique role.

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 clear context for when to use: 'for handoff to another session or agent'. Does not explicitly mention alternatives or exclusions, but the purpose is sufficiently distinct from the sibling tools to imply appropriate usage. Lacks an explicit 'use this instead of memo_get' but the context is clear.

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