read_memory

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

With no annotations, the description carries the behavioral disclosure burden. The verb 'Reads' makes it clear this is a non-mutating operation, and 'full content and metadata' sets expectations for what is returned. It does not mention error behavior or edge cases, but for a simple read operation the main behavioral trait is adequately disclosed.

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 compact and well-structured: a one-sentence purpose statement followed by a short Args list. Every sentence adds value, and the core action 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 two simple parameters, an output schema, and a read-only operation, the description is nearly complete. It explains what the tool does and what each parameter means. The only gap is the lack of explicit guidance on unknown IDs or alternative tool selection.

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 Args section adds real meaning beyond the input schema: memory_id is explained with an example, and workspace_dir is described as the workspace root with its default behavior. Since schema description coverage is 0%, this parameter documentation fully compensates.

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 states a clear verb ('Reads'), a specific resource ('memory entry from the workspace Memory Vault'), and the selection mechanism ('by ID'). It also says 'full content and metadata,' which distinguishes this from search_memory, which presumably finds entries without an ID.

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 phrase 'specific memory entry by ID' clearly implies this tool should be used when the caller already knows the memory_id. It does not explicitly mention alternatives or state when not to use it, so it stops short of full guidance, but the context is clear and unambiguous.

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