mempalace_add_drawer

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

The description adds behavioral context beyond the annotations by stating that content is stored exactly as provided and indexed semantically, and warns about the prefix. With annotations only indicating readOnly=false, this provides useful details about storage and indexing 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?

The description is two sentences, front-loaded with the core action, and every phrase earns its place. There is no redundancy or filler.

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 tool has an output schema, so return values are already defined. The description covers the main purpose, storage behavior, and a content formatting caution. It does not discuss deduplication or when to use update instead, but those are covered by sibling tools and are not essential for a basic add operation.

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 descriptions already cover all parameters (100% coverage), so the description does not need to repeat definitions. It adds some nuance about content being 'concise readable plain text or verbatim source content', but this is similar to the schema's description and does not significantly enhance parameter understanding.

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 uses the verb 'Add' and identifies the resource as a 'durable drawer' with content, clearly distinguishing it from sibling tools like delete, update, or list. It also specifies the action's scope by mentioning storing and indexing content.

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 description provides clear context: this tool is for adding new durable content, and it includes a specific usage instruction about not adding the AAAK prefix unless explicitly requested. However, it does not explicitly compare with alternatives such as mempalace_update_drawer or mempalace_check_duplicate, so exclusionary guidance is missing.

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