sage_inception

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

With no annotations, the description carries full burden for behavioral disclosure. It discloses that the tool checks for existing memories, seeds starter memories on new installations, and returns operating instructions. This provides sufficient behavioral context for an initialization tool.

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 concise with two sentences that convey all necessary information without unnecessary detail. It is front-loaded with the main action and includes key usage context.

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 no parameters and no output schema, the description provides complete context: what it does, when to call it, what it returns, and behavior for new vs returning users. The alias note is also 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?

There are no parameters, so schema coverage is 100% trivially. Baseline is 4 per guidelines. The description adds no parameter info but is rich in other context.

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 initializes a persistent memory session, distinguishing it from siblings by specifying it is for starting a new conversation. It uses specific verbs and resources, and mentions checking for existing memories and seeding starter memories.

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?

The description explicitly says to call this once at the start of every new conversation, which is clear usage guidance. It does not explicitly list when not to use or alternatives, but the context of being an initialization tool implies it should be used first.

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