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 without the text. The description adds only that this is an aggregated snapshot spanning several memory categories, which is mildly useful but omits scoping (per-user vs workspace), limits, or freshness of the snapshot.

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 sentences, content listed first and usage condition second, with no filler or restatement of the title. Every clause carries information.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does list the returned categories. It falls short on return shape (structured vs prose), ordering, or how complete the snapshot is, but it is adequate for a zero-param read tool whose annotations already cover safety.

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 takes zero parameters, so there is nothing for the description to clarify beyond what the empty schema shows. Baseline 4 applies for a no-argument tool.

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?

Gives a specific verb ("Returns") and enumerates the resource contents: active projects, open to-dos, recent decisions/intentions, and preferences. An agent can tell what it fetches, but the description never distinguishes it from nearby siblings like memory_get, memory_stats, or memory_surface, so it's clear-but-undifferentiated.

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?

Provides a concrete trigger: "when the first message of a conversation is about the user's work, clients or projects." That is a usable when-to-use signal, but it names no alternatives and no when-not conditions, so an agent still has to guess against memory_get or memory_list.

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