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

Annotations only provide readOnlyHint: false and destructiveHint: false, so the description carries the burden of behavioral context. It adds the key access restriction ('Players may not call this — GM/co-GM only') and scope (world background, factions, history). No contradiction with annotations. It does not detail side effects or rate limits, but the GM-only note is significant.

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 one sentence, front-loaded with the action and object, and includes only essential information (what it creates, who can call it). No fluff or redundancy.

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?

The description is adequate for a simple creation tool with a schema, but it omits the batch nature (items array, max 50) and does not explain how this relates to other mnemonic types. Given the large sibling list and the existence of an output schema, more context about the item format or usage scenarios would improve completeness.

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%, so the description should compensate, but it provides no parameter details. The parameter names (campaignId, items) are partially self-explanatory, but 'items' remains vague without the schema's inner structure. The description does not clarify that items is an array of mnemonic objects, leaving the agent to rely solely on the schema's property names.

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 tool creates 'Lore mnemons' and specifies content categories (world background, factions' beliefs, history). It distinguishes from sibling tools (e.g., create_archive_mnemons, create_custom_mnemons) by naming the lore type. The GM/co-GM restriction further clarifies the intended audience.

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 clear context that this is for lore-related mnemonics and is restricted to GM/co-GM, effectively saying who may call it. It does not explicitly name alternative tools or when not to use it, but the content examples imply when it is appropriate. A clear exclusion (e.g., 'for player-facing use, use create_custom_mnemons') would push it to 5.

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