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

With no annotations provided, the description carries full burden and delivers: it discloses the dossiers are pre-synthesized, the search ranking mechanism (BM25-ish), the optional type_filter behavior, the chronological list mode, and the important feature-flag behavior yielding an empty list without error. This is comprehensive behavioral disclosure.

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 dense but well-structured: it opens with a clear purpose, then usage context, then mode specifics, and finally a behavioral caveat. Every sentence contributes unique value, and no words are wasted.

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 tool's complexity (two modes, four parameters, feature flag behavior) and the presence of an output schema, the description covers all critical usage aspects: what it returns, how modes differ, ranking details, and edge-case behavior. It is complete without being bloated.

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 description coverage is 0%, so the description must compensate. It adds meaning for mode (search/list), query (BM25-ish ranking over summary+purpose), and type_filter (optional). However, the 'limit' parameter is not mentioned in the description at all, leaving a gap. Overall, it provides strong context for most parameters but not all.

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 the tool retrieves pre-synthesized per-session memory dossiers with typed metadata, distinguishing it from sibling tools that fetch raw memory or other session data. The verb 'Retrieve' and the specific resource 'per-session memory dossiers' make the purpose unmistakable.

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?

It explicitly states the intended use case ('multi-session or preference-style questions where stitching across conversations is the bottleneck') and describes the two modes. Although it doesn't name alternative tools, the context is clear enough to guide selection. Lacks explicit when-not-to-use guidance.

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