Get full memory by id

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds valuable details: redaction of <private> tags unless reveal_private=true (with audit event), token size range, and 'not found' returns for missing/soft-deleted ids. No contradictions.

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?

Very concise: first sentence states core purpose, second gives usage context, third explains behavioral nuance, fourth covers error case. No extraneous words, each sentence adds unique value.

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 output schema exists, description does not need to detail return structure. Covers purpose, usage, redaction, audit, error behavior, and token size. Fully sufficient for an agent to invoke correctly.

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 provides 100% coverage of descriptions. Tool description adds context: memory_id came from memory_store or memory_search, and reveals reveal_private triggers audit event. Adds value beyond schema without redundancy.

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?

Clear verb 'fetch' with specific resource 'memory by id'. Distinguishes from sibling tools like memory_search by specifying 'full body, tags, and metadata' and token range. Directly states read-only nature.

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?

Explicitly says 'Use after memory_search(detail="index") to expand a single hit', providing clear when-to-use context. Also warns about reveal_private usage emitting audit events. Lacks explicit mention of when not to use (e.g., for bulk operations) but implied by scope.

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