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

Annotations declare a mutating, non-idempotent, non-readonly operation, and the description adds real behavioral context beyond that: dialogs are suppressed, the return is raw JSON, and on module 8.14+ a self-targeted heal is applied with a result carrying status/appliedHealing or a no_roll_performed warning. It stops short of spelling out consumption semantics or failure modes, but the disclosure is well beyond what annotations carry.

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?

Three front-loaded clauses with no filler: the action, the sibling routing rule, and the 8.14+ edge case. Dense but each sentence carries distinct information; the version-gated note is slightly tucked at the end but still 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?

There is no output schema, so the description does the work of describing the return ('raw result as JSON' and the status/appliedHealing/warning fields). Combined with 100% schema coverage for inputs, an agent has enough to invoke and interpret results, though the consume side-effect and spell-slot interplay are left implicit.

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%, so the schema already documents all seven parameters (consume, scaling, activityId, showInChat, activityType, etc.). The description adds only the general 'target-free' framing, not parameter-level meaning, so the 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 ('Use an inventory item via item.use()') and enumerates the item categories it covers (potions, scrolls, spells, weapons, features). It explicitly distinsecs itself from the sibling dnd5e-item-activate, so an agent can route without opening either 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?

Provides an explicit when-to-use vs alternative rule: 'Quick, target-free use; dnd5e-item-activate when targets, AoE templates or Midi-QOL matter.' The selecting condition for the sibling is named, leaving little to inference.

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