marrow_get_memory

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

With no annotations, the description must disclose behavioral traits but only restates the operation. It does not mention side effects, authentication requirements, return format, error behavior (e.g., what happens if the ID does not exist), or whether this is a read-only operation beyond the implication of 'get'.

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 a single, front-loaded sentence with no redundant words. It efficiently communicates the core function without unnecessary elaboration.

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?

The tool is simple, but the description omits any detail about the return payload or edge-case behavior. Since no output schema or annotations are provided, additional context such as 'returns null if not found' or 'requires read access' would improve completeness, though the core purpose is clear.

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 fully documents the sole parameter 'id' as 'Memory ID' with 100% coverage. The description adds no additional semantic nuance beyond the schema, aligning with the baseline for high schema coverage.

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 'Get a single memory by ID,' specifying the action (get), resource (memory), and scope (single, by ID). This distinguishes it from sibling tools like marrow_list_memories (which returns multiple) and marrow_retrieve_memories (likely a search/batch 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 no guidance on when to use this tool versus alternatives such as marrow_retrieve_memories or marrow_list_memories. It does not mention any prerequisites, exclusions, or conditions under which a different tool should be preferred.

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