memory_disable

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

With no annotations, the description carries the full burden, and it delivers: it discloses flushing the reactor queue, removing all lambdacad memory reactors application-wide, stopping bracketing, and confirming tags/journal files stay untouched. This is rich, non-destructive behavioral detail.

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 front-loaded with the main purpose, followed by a compact paragraph of essential behavioral details. Every sentence contributes meaningful information without redundancy, making it appropriately concise for the tool's complexity.

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 zero-parameter tool with no annotations, the description covers purpose, side effects, scope (application-wide), and exceptions (tags/journal files untouched). The existence of an output schema handles return values, so this is complete.

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 tool has zero parameters, so the baseline is 4. The description adds semantic value by explaining what 'disable' does beyond the schema, making the empty schema irrelevant.

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 opens with 'Turn the drawing's memory journal OFF, cleanly,' which is a specific verb+resource statement. It further clarifies the scope (application-wide) and the action (flushing, removing reactors), clearly distinguishing it from sibling tools like memory_enable.

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 clearly implies this is for disabling the memory journal and provides context about the cleanup process, but it does not explicitly mention alternatives (e.g., memory_enable) or state when not to use it. This meets 'clear context, no exclusions'.

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