memory_inspect

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

With no annotations, the description carries the behavioral burden. 'Inspect' strongly implies a read-only operation and 'user-friendly way' suggests a human-readable result, which is useful. However, it does not explicitly state whether there are side effects, permissions, or formatting caveats, so transparency is partial.

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 a single concise sentence with no filler. It front-loads the main action and adds a relevant detail about the output, though slightly more structure could clarify parameter usage.

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?

Despite an output schema and optional parameters, the description leaves out essential invocation context: how to identify the target record, when to prefer this over memory_probe/memory_explain, and any behavioral caveats. The tool is simple-sounding, but the undocumented parameters make it incomplete.

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% and the description adds no meaning to the three parameters. An agent cannot determine what id, entity, and property represent, how they combine, or which are needed to identify a memory record. This is a critical gap.

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 uses a specific verb ('Inspect') and resource ('a memory record'), and clarifies the output scope by mentioning preview, payload, and relations. It is clear enough to distinguish from list/add/update/remove siblings, though it does not explicitly differentiate from similar inspection tools like memory_probe or memory_explain.

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 guidance on when to use this tool versus alternatives. The description does not state any preconditions, exclusions, or preferred contexts, leaving the agent to infer applicability from the tool name alone.

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