mcp_engram_turn_record

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

Discloses what is captured (user utterance, assistant output, auto-aggregated traces). However, no annotations are provided, and the description does not mention auth requirements, side effects, or behavior on repeated calls, leaving gaps.

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 wasted words. Front-loaded with core action and key details. Highly efficient.

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?

For a tool with 15 parameters and no output schema, the description provides a high-level overview but lacks detail on return values, prerequisites, or error conditions. Adequate but not comprehensive.

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 80%, and the schema already describes parameters well. The description adds no extra parameter detail, so baseline score applies.

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?

Clearly states it mints an RPT v3 agent_response turn tile, specifying the schema version. Differentiates from sibling tools by focusing on recording turn interactions, extending prior convention.

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 at end of each assistant turn (lean default)', providing clear context. Does not list alternatives or when not to use, but the instruction is specific enough.

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