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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully adds that memories are scoped to the person on this connection and the workspace, and that each item includes its ID. It does not describe return formatting or pagination, but for a zero-parameter read tool this is minor.

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?

Three compact sentences, front-loaded with the core purpose and memory categories. The follow-on guidance about session-start use and sibling tools is useful and earns its place without repetition.

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 zero-parameter, read-only list tool with no output schema and strong annotations, the description is complete enough. It covers scope, content categories, ID exposure, intended session-start usage, and the alternative tools for adjacent operations.

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 zero parameters, so there is no parameter semantics needed and the baseline is 4. The description appropriately focuses on what is listed rather than inventing parameter details.

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?

Starts with a specific verb and resource: 'List what SkipCalls remembers...' and enumerates the memory categories (name, preferences, standing rules, links, date-bound facts). It clearly distinguishes itself from the sibling memory tools by naming memory_remember and memory_forget for different operations.

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 says to read it 'at the start of a session to follow the saved preferences,' giving a clear when-to-use condition. It also routes the agent to the correct siblings for saving and deleting memories, leaving little inference required.

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