sage_inception

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

With no annotations provided, the description carries the full burden. It discloses that it 'checks if you already have stored memories and returns your operating instructions' and on a brand-new installation 'seeds starter memories about how to use the memory system effectively.' This explains key side effects and outputs, though it does not address idempotency or potential consequences of calling it multiple times.

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 three focused sentences, front-loaded with the action ('Initialize your persistent memory session'), then usage timing, then behavior. Every sentence adds unique value with no redundancy or fluff.

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 tool's simplicity (no parameters, no output schema), the description is complete. It covers purpose, when to use, what happens on existing vs. new installs, and the return value ('returns your operating instructions'). No additional context is needed.

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?

The tool has 0 parameters and schema description coverage is 100%. Per the baseline for 0 parameters, a score of 4 is appropriate. The description adds no parameter-specific details because there are none to describe.

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 uses a specific verb 'Initialize' and resource 'persistent memory session', and clarifies scope as 'start of every new conversation with SAGE', distinguishing it from sibling tools like sage_remember or sage_recall. It clearly states what the tool does and its role in the system.

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 states when to call: 'Call this once at the start of every new conversation with SAGE.' This provides clear usage context. However, it does not explicitly mention when not to use it or name alternatives, though the context implies its exclusive role at conversation start.

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