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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses important behavioral details: authentication requirement, path traversal blocking, and filename validation rules. These add significant context beyond what annotations provide.

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 has redundancy: it repeats the persistence purpose, filename constraint, and path traversal blocking. While the first sentence is front-loaded and clear, the repetition inflates the length without adding new information.

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 largely complete for a write tool: it explains purpose, usage context, filename requirements, authentication, and security blocking. The existence of an output schema reduces the need to describe return values. Minor gaps include not explaining overwrite behavior, but overall adequate.

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%, but the description adds meaningful constraints not in the schema: filename must contain only lowercase letters, digits, underscores, and hyphens, and must end in .md. It also provides examples. This enriches parameter understanding beyond the schema.

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 ('Write or update') and resource ('Claude Code project memory file (.md)'), and clearly states what it persists (project context, user preferences, feedback). It distinguishes itself from the sibling tool thinkneo_read_memory by focusing on the write/update operation.

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 states when to use: 'Use this to persist project context, user preferences, feedback, and reference notes across Claude Code sessions.' It does not provide explicit alternatives or when-not-to-use instructions, but the context is clear enough.

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