memory_consciousness

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

No annotations are provided, so the description must disclose side effects. It says 'gets written to CLAUDE.md', implying a file write, but does not mention whether it overwrites existing content, requires prior memory state, or changes anything else. This is a significant transparency gap for a potentially mutating operation.

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?

Two short sentences, front-loaded with the main action and a clarifying detail. No wasted words, and the connection to CLAUDE.md adds value without verbose explanation.

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 description is sufficient for a zero-parameter tool in terms of basic function, but it lacks guidance on when to run it, what happens to existing CLAUDE.md content, and how this relates to the memory lifecycle (init, save, consolidate). Without annotations or an output schema, it should provide at least a note about side effects.

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 0 parameters, so the schema provides no parameter descriptions. The baseline for tools with no params is 4, and the description adds relevant context about the output destination ('written to CLAUDE.md'), which is useful for understanding the tool's behavior.

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 'Generate' and names the resource 'the full consciousness document', then ties it to a concrete output location ('written to CLAUDE.md'). This clearly distinguishes it from the sibling memory tools, which focus on saving/recalling/searching memory items rather than producing the overall consciousness document.

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?

No explicit guidance on when to use this tool versus alternatives. The only contextual hint is that it generates the consciousness document that gets written to CLAUDE.md, but it doesn't state prerequisites, ordering, or situations where this is preferred over memory_init or memory_consolidate.

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