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

With annotations already declaring readOnlyHint, idempotentHint, and destructiveHint=false, the description adds meaningful behavioral detail by specifying the two invocation modes and what each returns (index vs full content). It doesn't contradict annotations and provides additional context beyond them.

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 concise, two sentences total, with the verb and resource in the first sentence. It is front-loaded with the primary purpose and uses clean, purposeful language without unnecessary detail.

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 simple read tool with one optional parameter, the description covers all necessary aspects together with rich annotations and a complete schema. It explains both usage modes and the type of content accessible, making it fully adequate for an agent to select and invoke correctly.

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 input schema already provides 100% coverage with a detailed description of the 'filename' parameter, including examples and default behavior. The tool description reinforces this by explaining the two modes, which adds slight value by framing the parameter's role in the overall operation.

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 ('Read') and resource ('Claude Code project memory files'), and clearly explains two modes: returning the MEMORY.md index without arguments or the full content with a filename. It effectively distinguishes from sibling tools like thinkneo_write_memory by focusing on the read 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?

The description provides clear context on when to use the tool: to access project context, user preferences, feedback, and reference notes. It doesn't explicitly name alternatives or state 'when not to use', but the read/write distinction from siblings is evident and the use case description is sufficient.

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