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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses two non-obvious behaviors: results are scoped to namespaces the handle has explicitly written to (privacy model), and a registered handle plus secret are required for auth. It also notes deleted entries are returned, which matters for sync reconciliation.

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 with the core purpose front-loaded after a short store tag. No filler, though the bracketed '[stores]' prefix is minor noise.

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 adequately conveys what comes back (created/updated/deleted entries) and the auth and scoping constraints. Pagination detail lives in the schema's limit param, so an agent has enough to invoke it correctly.

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 coverage is 60% (limit, since, namespace documented), and the description compensates for the undocumented handle/secret by requiring a registered handle and secret and anchoring 'since' to a timestamp. It adds meaning beyond the schema rather than restating it.

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?

States a specific verb and resource: returns memory entries created, updated, or deleted since a timestamp, framed as 'Incremental sync'. This clearly distinguishes it from siblings like search_memory, list_memory, and memory_stats without needing to name them.

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?

The 'Incremental sync' framing tells the agent the use case (catch-up after a timestamp) versus full listings or searches. It lacks an explicit when-not or a named alternative, but the sync framing is strong enough to imply correct selection.

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