Dereference a memory_token in one round-trip

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds context: returns parsed cell+fact_cid, full fact body, stable fact_url, and 404 with typed code. No contradiction; adds value beyond annotations.

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?

Description is two concise paragraphs: first explains functionality, second provides usage guidance. No wasted words, front-loaded with purpose.

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 one parameter, no output schema, but annotations cover safety. Description covers what the tool returns (parsed parts, fact body, fact_url) and error handling (404 with typed code). Complete for a dereference tool.

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 coverage is 100% and the schema description already clearly defines the token parameter format. The main description reinforces but does not add new semantic meaning beyond what the schema provides.

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?

Title and description clearly state the tool dereferences a memory_token to return the signed fact body. It distinguishes from siblings like emem_memory_token (creates tokens) and emem_entity_resolve (resolves entities) by specifying its unique function.

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?

Explicit 'When to use' paragraph tells agents to call when receiving a memory_token from another agent or previous turn. Also provides alternatives on 404 error (try /v1/fetch with cid or paste at mirror).

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