init_memento

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

No annotations are provided, so the description carries the full burden. The 'MANDATORY' all-caps framing conveys that this is a required prelude that loads state, but it doesn't disclose what side effects occur (e.g., does calling it twice reset state? does it create server-side sessions? what is the return value?) The behavior 'loads all mementos' is stated but minimal detail is given about what initialization actually entails beyond the get_mementos redundancy note.

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 one long sentence that packs in imperative instruction, usage guidance, and the redundancy note. It's reasonably concise and front-loads the critical mandate, but the all-caps shouting and the run-on structure makes it slightly harder to parse. It earns its sentences but could be cleaner.

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 an initialization tool with zero required params and no output schema, the description covers the critical usage context (when to call, that it loads state). However, it doesn't explain what the tool returns, whether it's safe/idempotent to call repeatedly, or the nature of the 'memento' state being loaded, which would be useful for a first-call setup tool.

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% and there is only one optional parameter. The description adds meaning to repo_path by explaining the scoping behavior ('scoped memory tied to this path instead of server's working directory'), which goes beyond the schema's phrasing. This adds genuine value to the single 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 states the tool initializes/loads mementos and is the mandatory first call, but the core purpose ('initializes a memento session/context') is only implied through the imperative framing and the parenthetical about loading mementos. It distinguishes from get_mementos by noting calling both is redundant, which provides sibling differentiation.

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 gives extremely explicit usage guidance: ALWAYS first action, every session, no exceptions, before greetings or simple questions. It also explicitly tells the agent NOT to call get_mementos after since it would be redundant—clear when-not guidance naming a specific sibling alternative.

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