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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by disclosing transactional semantics: all-or-nothing validation (section exists, each slug free and unique within the batch), abort-on-clash that names the failing item, and mid-batch rollback. This is exactly the kind of behavioral context annotations cannot convey.

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-loads the core purpose in the first clause, then layers on transaction semantics and the memId format note. Dense but every sentence carries useful information; slightly long for a two-parameter tool, though nothing is filler.

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?

With no output schema, the description carries return-value opacity, but for a batch attach tool the important call-time concerns (validation order, abort behavior, rollback, id format) are all covered. The only minor gap is not describing what a successful call returns.

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 parentKey and every children field. The description adds marginal value by noting memIds accept full or short-form prefixes and by restating the batch-uniqueness of slugs, but this largely duplicates the schema. 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 MANY existing memories to a bundle under ONE section in a single call') and immediately distinguishes itself from the sibling muninn_bundle_node_create by framing itself as the batch alternative. An agent can tell exactly what this does without opening the 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?

Names the alternative explicitly ('instead of one muninn_bundle_node_create per item'), which gives clear selection context. No explicit when-not condition is stated, but the batch framing makes the intended usage unambiguous.

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