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

With no annotations, the description carries the full behavioral burden. It does disclose one real behavior — episodes are shared org-wide by default — which is genuine value, but it says nothing about read-only status, pagination limits (limit defaults to 20, max 200), ordering, or auth requirements.

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?

A single front-loaded sentence with the scope caveat in parentheses and zero wasted words. Nothing is buried and nothing needs trimming.

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?

An output schema exists, so return values need not be described, and the sharing scope is stated. However, for a 5-parameter browsing tool in a very crowded memory tool family, the lack of routing guidance and pagination/ordering context leaves meaningful gaps.

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 80% and the parameters (agent, topic, since, until, limit) are each documented in the schema, so the baseline is 3. The description adds no filter syntax, matching semantics, or default-override detail beyond the 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?

The description states a specific verb ("Browse") and resource ("episodic timeline"), so an agent can tell this is a listing tool for episode history. It stops short of naming a sibling (e.g. memory_recall, memory_changes_since) to disambiguate the many other memory_* read tools.

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?

There is no when-to-use guidance and no exclusions. It never explains how this differs from memory_recall, memory_changes_since, or memory_get, all of which plausibly retrieve stored memory, so the agent must guess which read tool fits.

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