set_memory_context

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

With no annotations, the description carries the full burden, and it does disclose the key risk-limiting trait: the change is confined to a single conversation and does not alter the connection default. However, it says nothing about authorization, idempotency, invalid/missing space handling, or error behavior for a mutation 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?

A single sentence with zero filler, and the scope constraint is front-loaded. It is efficient for the minimum it says, though brevity here borders on under-specification.

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 two-parameter mutator with no annotations and no output schema, the description covers the intent and blast radius but omits what the call returns, what happens on success/failure, and whether the session or space must pre-exist. Adequate but with clear gaps.

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% and neither parameter has a description. The description's words 'conversation' and 'space' loosely map to session_id and space_id but add no format, ID type, or validity requirements, so the agent must infer both parameters from their names alone.

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 (change) and a precisely scoped resource (one conversation's active space), and clarifies the boundary versus the connection default. It implicitly distinguishes from the sibling get_memory_context by being the mutating setter, though it never names that sibling.

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?

Usage is only implied: the 'without changing connection default' clause hints at when this is preferred over a connection-wide change, but there is no explicit when-to-use, when-not, or named alternative tool.

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