memory_explain

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

No annotations (e.g., readOnlyHint, destructiveHint) are provided, and the description does not mention side effects, permissions, or return behavior. It is unclear whether this tool only reads data or modifies anything.

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 redundant words. It directly states the tool's purpose without unnecessary detail.

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 simple tool this description is minimally adequate, but it lacks context about the output format or any additional behavior. The missing parameter details and return expectations reduce completeness.

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?

The single parameter node_id has no schema description and is not elaborated in the tool description. This leaves ambiguity about what node_id refers to and how it should be supplied.

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 clearly states the action (explain) and the resource (a memory's score breakdown), distinguishing it from sibling tools like memory_store or memory_search. It is specific enough to understand the purpose.

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?

No explicit guidance is given on when to use this tool versus alternatives. The description implies use when wanting to understand a memory's score, but does not state conditions or prerequisites.

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