rememb_read

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 effectively describes key traits: 'Safe, read-only operation with no side effects' clarifies safety and mutability, and 'Use this at the start of every session to load context' implies it's foundational for initialization. However, it doesn't mention potential limitations like rate limits, pagination, or error conditions.

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 highly concise and well-structured with three sentences that each serve a distinct purpose: stating the core functionality, describing behavioral traits, and providing usage guidelines. There is no wasted language, and key information is front-loaded.

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 tool's low complexity (1 optional parameter, no output schema, no annotations), the description is mostly complete. It covers purpose, safety, and usage guidelines effectively. However, it lacks details on output format (e.g., what 'memory entries' look like) and doesn't address potential edge cases, which would be helpful despite the absence of an output schema.

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 description coverage is 100%, so the schema already fully documents the single parameter with its enum values. The description adds minimal value beyond the schema by mentioning 'filter by section' but doesn't provide additional context about parameter usage or implications. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the tool's purpose with specific verbs ('Read all memory entries or filter by section') and distinguishes it from siblings by contrasting with 'rememb_search' for keyword-based queries. It explicitly identifies the resource ('memory entries') and scope ('all' or filtered).

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 explicit guidance on when to use this tool ('Use this at the start of every session to load context') and when to prefer an alternative ('Prefer rememb_search when looking for specific information by keyword or topic'). It clearly differentiates use cases between loading general context versus targeted searches.

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