memory_slot_append

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

With no annotations, the description carries the full burden and meets it: it discloses newline insertion, audit recording, the success/return shape, failure cases (missing or read-only slot, sizeLimit overflow), that overflow leaves content unchanged, and project-slot shadowing of global slots.

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?

Front-loaded with the core action, then failure modes and routing. Dense but every clause is relevant; the semicolon-chained sentences pack a lot without waste, though they are slightly heavy.

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?

No output schema or annotations exist, yet the description covers return values, edge cases, overflow semantics, and the label-namespace interaction. Nothing needed to invoke it correctly is missing for a simple two-parameter tool.

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 both parameters are already documented, setting a baseline of 3. The description adds real meaning to 'label' by explaining that project slots shadow global slots with the same label, which the schema does not convey.

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?

States a specific verb and resource ('Append text to an existing effective slot') plus two behavioral details (newline insertion, audit entry). It is immediately distinguishable from siblings memory_slot_create, memory_slot_replace, and memory_slot_delete.

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 routes to alternatives under named conditions: memory_slot_replace when overflow needs compaction, and memory_slot_create when the label does not exist. Repeated-call behavior is also called out, leaving nothing to inference.

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