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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds valuable behavioral details: the auto-detach consequence when required fields are omitted, and the permission boundary. This goes beyond the minimal annotation disclosure.

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 compact—three sentences, each containing essential information. The first sentence states the core purpose, the second gives conditional parameter guidance, and the third covers permissions. No filler or redundant content.

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?

Given the tool's complexity (multiple playerKind values, required parent/party/character IDs, permission nuances) and the presence of an output schema, the description sufficiently addresses the main complexities. It could mention the enum values for playerKind/visibility, but these are already in the schema. Overall, it provides enough context for correct use.

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?

Although the schema description coverage is listed as 0%, the actual schema includes descriptions for several parameters (partyId, markdown, characterId, parentEntryId). The tool description further clarifies the conditional semantics of parentEntryId, partyId, and characterId for playerKind=CHARACTER, adding meaning beyond the schema's field-level descriptions.

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 uses a specific verb 'Create' and clearly identifies the resource 'Player mnemons', enumerating the distinct types (party root, character notes, party notes). It differentiates this tool from sibling create_*_mnemons tools by focusing on 'player' mnemons.

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 provides clear conditions for when to use the tool, especially for playerKind=CHARACTER, listing required fields and the auto-detachment behavior. It also specifies permission requirements (players with campaign.write vs GMs). It doesn't explicitly mention alternatives, but the context and field conditions offer solid usage guidance.

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