memory_flush

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal the key behavior—flushing pending entries and reindexing—but says nothing about idempotency, side effects, locking, failure modes, or whether the operation is safe to repeat.

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 English description is a single, front-loaded sentence that communicates the action and its consequence efficiently. The bilingual duplicate adds some redundancy but does not harm clarity.

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 action tool, the description covers the core behavior and the reindexing side effect. However, since there is no output schema and no usage guidance, an agent is left without information about expected return values or when this flush is necessary versus automatic.

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 and the input schema is completely covered at 100%, so there is nothing meaningful for the description to add about parameters. The baseline of 4 is appropriate here.

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 a specific verb ('Trigger immediate distribution') and names a concrete resource ('pending write_log entries' to '.md files'), plus a clear follow-up action ('then reindex'). This distinguishes it from related sibling tools like memory_write or memory_search, making the tool's purpose unambiguous.

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 'pending write_log entries' and 'immediate' imply this tool is used to force materialization of queued writes and rebuild the index. However, it never explicitly states when to use it versus memory_write or when not to use it, leaving the routing decision mostly to inference.

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