rememb_read

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

Declares the operation as safe and read-only with no side effects, which is sufficient given no annotations. Could mention response formatting or limits, but the parameter max_chars hints at content control.

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?

Three concise sentences covering purpose, safety, usage guideline, and sibling differentiation. No superfluous text.

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?

Given the simplicity of the tool (3 parameters, no output schema), the description provides adequate context: purpose, safety, usage recommendation, and comparison to sibling. Minor omission: default behavior when no section is specified (reads all) is implied but not explicit.

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% with detailed parameter descriptions. The tool description only restates the filtering capability, adding no new semantic information 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?

Clearly states the tool reads memory entries, with optional filtering by section. Differentiates from sibling rememb_search by specifying its use for keyword search.

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?

Provides explicit when-to-use advice (start of every session to load context) and when to prefer alternative (rememb_search for specific keywords). This fully addresses usage context.

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