add_memo

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys that this is a write/create action but does not describe return values, duplicate handling, persistence behavior, or any side effects beyond the implied save. It also mostly restates what the schema already exposes.

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?

A single sentence with no filler; the key action ('Save a new') and scope ('context memo, snippet, or idea') are front-loaded, and optional modifiers are included succinctly. Every part earns its place.

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?

For a simple creation tool with an output schema available, the description plus input schema is nearly sufficient: required title/content and optional category/tags are covered. It lacks explicit sibling routing and behavior details, but those are handled in other dimensions, and the tool's complexity is low.

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 description coverage is 0%, so the description must compensate. It adds that category and tags are optional and frames the content as a context memo, snippet, or idea. However, it does not explain the meaning or expected format of the required title and content parameters beyond their obvious names.

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 a specific action ('Save'), a concrete resource (a new context memo/snippet/idea), and the optional category/tags. It clearly distinguishes this creation tool from the list/get/search/delete/clear sibling tools, even without naming them.

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?

The phrase 'Save a new ...' implies this tool is for adding new memos rather than retrieving or managing existing ones, but it does not explicitly state when to prefer this tool over alternatives or mention any exclusion criteria. Usage context is implied, not spelled out.

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