Session instructions (mem alias)

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

The description lists write actions like push, ack, clear, checkpoint, but annotations include readOnlyHint=true, indicating the tool should not modify state. This is a direct contradiction, severely misleading the agent.

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 very short but covers the basics. However, it omits necessary details about each action, making it barely adequate.

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 complexity (8 actions, 9 parameters) and no output schema, the description fails to explain the behavior of each action, prerequisites, or return values. The annotation contradiction further undermines completeness.

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?

All 9 parameters have descriptions in the input schema (100% coverage), so the description adds minimal value beyond listing actions. The description does not explain parameter usage or relationships.

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 it's an alias of instruct for session-scoped instruction cache operations, and lists the available actions. This provides a clear purpose, though it doesn't differentiate from the sibling 'instruct' tool beyond being an alias.

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?

No guidance is given on when to use this tool versus alternatives, nor on when to use specific actions. The description lacks context for decision-making.

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