mcp_engram_read_concept

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

Discloses that it fetches the complete original document and bypasses search, and explains the truncation behavior of recall. However, no mention of error handling or output format, and no annotations to supplement.

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?

Two sentences, no redundant information, front-loaded with purpose and trigger. Every sentence adds 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 low complexity, one parameter, and no output schema, the description adequately covers when and why to use the tool. However, it fails to describe the return value or potential errors, which would be helpful.

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 already provides a good description for the single parameter 'concept'. The tool description adds minimal extra meaning beyond stating it's for a 'specific memory block', meeting the baseline.

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 reads the full text of a memory block, distinguishes it from 'recall' which only provides a 512-character snippet, and specifies the trigger condition.

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 when to use (after recall, when full text is needed) and indicates when not (when snippet is sufficient), and references the alternative tool (recall).

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