mcp_engram_pin

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

With no annotations, the description carries the burden. It discloses setting CRS to 1.0, locking from eviction, and that pinned blocks still support relate/update. It could mention reversibility but is otherwise transparent.

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 two sentences plus a structured 'WHEN TO USE' section. Every sentence adds value, and the key action is front-loaded. No wasted words.

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 the simple one-parameter tool and no output schema, the description adequately covers purpose, effects, and usage guidance. It lacks details on error handling but is complete enough for an AI agent.

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% for the single parameter 'concept'. The description adds minimal extra meaning beyond the schema's description (e.g., examples of tags). Baseline 3 is appropriate as the schema already adequately documents the parameter.

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 sets a concept's CRS to 1.0 and locks it to prevent eviction by the Autophagy Daemon. It specifies the action on a specific resource (concept) and distinguishes from siblings like forget_old.

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 provides 'WHEN TO USE' with examples (foundational knowledge) and 'Do NOT pin everything' with rationale. It also mentions an alternative tool (mcp_engram_forget_old) for cleanup, offering clear guidance.

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