Rememb

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool reads memory entries and can filter by section, but lacks details on permissions, rate limits, pagination, or what 'memory entries' entail (e.g., format, size). For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves beyond basic functionality.

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 and well-structured in two sentences: the first states the purpose, and the second provides usage guidelines. Every sentence earns its place by adding clear value, with no wasted words or redundancy, making it easy for an agent to parse and understand quickly.

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 somewhat complete but has gaps. It covers purpose and usage well, but without annotations or output schema, it lacks details on behavioral traits (e.g., read safety, response format) and what 'memory entries' contain. This makes it adequate but not fully comprehensive for an agent to use confidently.

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 has 100% description coverage, with the 'section' parameter fully documented via enum and description. The description adds minimal value beyond the schema by mentioning 'filter by section,' which is already covered. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't provide additional semantic context (e.g., what each section means or how filtering works).

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: 'Read all memory entries or filter by section.' It specifies the verb ('Read') and resource ('memory entries'), and distinguishes it from siblings by focusing on reading rather than writing, clearing, deleting, editing, initializing, or searching. However, it doesn't explicitly differentiate from 'rememb_search' in terms of filtering vs. searching, which slightly reduces clarity.

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 usage guidance: 'Use this at the start of every session to load context.' This tells the agent when to use the tool (at session start) and implies its role in context loading, which is helpful for distinguishing it from other tools like 'rememb_search' or 'rememb_write' that might be used later or for different purposes.

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