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

With no annotations provided, the description carries the full disclosure burden. It does disclose the core behavioral trait (a destructive replace with create-if-needed semantics) and the org-shared scope, which is useful. However, it omits any mention of permissions, reversibility, or side effects on related memory entities, so behavioral disclosure remains thin.

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 front-loaded sentence with a parenthetical that adds meaningful upsert context. It contains no filler and 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?

For a straightforward set operation, the description covers the core function, and the output schema plus fully documented parameters provide much of the necessary context. But the large memory_* sibling family includes memory_agent_ensure, which likely overlaps, and without usage/alternative guidance or side-effect disclosure an agent may route incorrectly. Operationally adequate, contextually under-specified.

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 each parameter already documented: body_md is described as a compressed, org-visible markdown profile; name, slug, agent, and cursor_agent_id are optional attribution labels. The tool description adds no meaning beyond schema, so the baseline score of 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?

The description states a specific verb ('Replace') and resource ('an agent's org-shared memory profile'), and adds the upsert qualifier 'creates the entity if needed.' This makes the tool's function clear and distinguishes it from read-oriented siblings like memory_agent_get and memory_agent_list, but it does not explicitly contrast it with similar write/ensure siblings such as memory_agent_ensure.

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 description gives no guidance on when to use this tool versus the closely related memory_agent_ensure or other memory set tools like memory_soul_set, memory_playbook_set, or memory_procedure_set. There are no exclusions, prerequisites, or alternative conditions, leaving the agent to infer usage solely from the verb 'Replace.'

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