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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description only needs to add context — and it does: it discloses the duplicate-slug failure mode and explains that 'contains' is a single canonical home versus a second 'reference' link. It stops short of describing the response payload or what position/ordering guarantees apply on append.

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?

Front-loaded with the action and scope, and every sentence carries information. It is slightly long and duplicates the okfType and relation explanations that already live in the schema, which is the only waste.

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 mutation with no output schema, the description should say what comes back (presumably the created node or its key) so the agent can chain follow-up calls like node_repoint or render_bundle. Ordering behavior on append ('Omit to append') is left entirely to the schema, and the relationship to muninn_bundle_nodes_create is unaddressed.

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 100%, so the schema already documents all six parameters, including okfType and relation. The description restates the okfType values and relation semantics but adds no new meaning, and it never mentions position, memId, or parentKey beyond the vague 'under a section'. Baseline 3 is appropriate.

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 and resource ('Add an existing memory to a bundle... as an item under a section') and parenthetically defines what a bundle is. It also explicitly distinguishes itself from muninn_bundle_create, so an agent can separate the two without opening a schema.

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?

'Use it to place something the user already wrote, such as a chapter's full text or its summary' gives a concrete use case, and the sentence contrasting with muninn_bundle_create routes the agent away from the wrong tool. It does not address the near-sibling muninn_bundle_nodes_create (bulk/plural variant), which is the most likely confusion.

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