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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description adds real behavior beyond that: append-only semantics, de-duplication of both pre-existing and in-batch repeats, the `skipped_duplicates` return key, undo availability from the same surface, and the absence of a plan_token.

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 core instructions are front-loaded and efficient, with the batch alternative stated in the first three sentences. The CONFIRMATION paragraph is longer than needed and reads as reusable boilerplate, though it does carry the undo/plan_token distinction.

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 single-parameter write tool with no output schema, the definition covers input shape, duplicate handling, and return behavior (`skipped_duplicates`). An agent has everything needed to call it correctly without further inference.

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 0%, so the description must carry the load and largely does: it specifies that `items` accepts either plain strings or `{content, tags}` objects, which the schema alone does not reveal. It stops short of describing tag format or the 100-item limit, leaving minor gaps.

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?

Opens with a specific verb and resource plus scope: "Store SEVERAL memory facts at once (batch remember) in the caller's workspace." This immediately distinguishes it from the singular `remember` sibling by making the batch nature the defining trait.

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?

"Use this instead of many remember calls" names the alternative explicitly and gives the condition that selects it. The CONFIRMATION block further clarifies that this specific tool executes immediately rather than proposing, contrasting it with destructive/outbound/financial operations.

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