remind_session

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

Mentions the operation is cheap (~1 KB) and provides summary content. No annotations provided, so description carries burden; it could explicitly state read-only/no side effects, but the nature is implied.

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?

Two concise paragraphs: first states purpose and content, second provides when-to-use. No waste, front-loaded with essential info.

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 simple 1-param tool without output schema, the description covers purpose, usage context, and parameter details completely. Sibling references are included.

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 covers sessionId with description; description adds practical guidance that prefix is enough, which adds value beyond schema.

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?

Clearly states the tool retrieves a structured summary of a past session with specific content (title, message count, tool names, etc.). Differentiates from sibling `remind_message` for message bodies.

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 advises using after a `remind_search` hit to get the bigger picture, and directs to `remind_message` for message bodies. Also clarifies that an 8-char prefix sessionId is sufficient.

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