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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower, yet the description still adds real value: the note is deliberately content-free, it is routed to the Engram team, and sensitive payloads must be excluded. It stops short of describing the write's result or any rate/duplication behavior.

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, zero filler, with the core action and scope front-loaded and the privacy constraint placed as the closing guardrail. Every clause earns its place.

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?

There is no output schema, but the tool is a simple append-style log, and the description covers purpose, triggers, and the sensitive-data constraint. Minor gaps remain on whether the call returns an id or dedupes repeats, which an agent could want in order to verify the log landed.

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 100% with enums spelled out for kind and severity, so the schema already carries parameter meaning. The description only reinforces the 'content-free' rule for detail, adding no format, default, or unit information beyond the schema, so the baseline 3 applies.

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 (records) and resource (a short, content-free note) plus the triggering situations (build, daily update, session). An agent can distinguish this diagnostic-logging tool from memory/session siblings like memory_append or run_checkpoint without opening the schema.

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?

Enumerates concrete when-to-use triggers (refusal, retry, stall, tool or environment error) and gives a clear when-not constraint ('Never include message bodies, names or query text'). It does not name a competing sibling to route against, which keeps it from a 5.

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