configure_memory

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

With no annotations, the description carries the full burden. 'Configure' implies a mutation, but there is no disclosure of persistence behavior, whether settings are merged or overridden, how global vs per-session scopes interact, or any validation or error behavior. This lack of context is a significant gap for a configuration tool.

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 sentence with a clear verb, noun, and scope parenthetical. Every word earns its place; no redundancy or fluff.

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?

An output schema exists, so return value details are not necessary, but the description is too thin overall. It does not explain the tool's effect on memory configuration, how it relates to configure_brain, or what happens when the embedding/rerank objects are omitted. For a tool with two open-object parameters and zero annotations, more context is needed.

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 parameters are open objects. The description adds minimal value by linking 'embedding' and 'rerank' to the corresponding settings and 'per-session' to session_id, but it does not clarify the expected fields inside the embedding/rerank objects or how session_id controls scope.

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 verb 'Configure' and the resource 'memory embedding/rerank settings', with a scope indication of 'global or per-session'. It identifies the tool's function distinctly from memory retrieval tools, though it does not explicitly differentiate from sibling 'configure_brain'.

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 parenthetical '(global or per-session)' gives a hint about scope options, implying session_id usage, but the description provides no guidance on when to use this tool over configure_brain or other configuration tools. No when-not-to-use or alternatives are mentioned.

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