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

The description discloses that dialogs are suppressed and that it returns the raw use result as JSON, which are behavioral traits. However, it does not explicitly state the side effects of using an item, such as whether consumables are actually consumed or spell slots are expended. Since all annotations are false (readOnlyHint, destructiveHint, idempotentHint), the description carries the full burden, and it only partially covers the behavioral implications. It mentions the consume parameter indirectly through the schema but not in the description itself. This is a moderate gap.

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 two sentences plus the differentiation clause, all front-loaded with the purpose and usage guidance. There is zero wasted text; every sentence earns its place by either stating what the tool does or when to use it. The structure is efficient and scannable.

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 tool with 7 parameters and no output schema, the description covers the essential contextual information: what it does, when to use it, and what it returns. It does not explain error cases or prerequisites (e.g., the actor must own the item), but these are fairly obvious from the domain. The differentiation from the sibling and the note about 'without targets' covers the main usage constraints. Given the complexity, this is reasonably complete, though it could mention that using an item may have permanent game-state effects.

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?

The schema has 100% description coverage for all 7 parameters, so the schema already documents each parameter's meaning. The description adds minimal additional parameter semantics—it mentions the item types supported and the 'dialog-free' nature, but does not clarify parameter interactions or provide examples. This is exactly the baseline where the schema does the heavy lifting, so a score of 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?

The description clearly states the tool's action (use an item via item.use()), the resource (actor's inventory), and the scope (consumables, spells, weapons, features). It also explicitly differentiates from the sibling dnd5e-item-activate by naming the alternative and the conditions that select it. This makes the purpose unambiguous and distinct from similar tools.

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 explicit usage guidance by stating 'CHOOSING: this tool for quick, dialog-free usage without targets; dnd5e-item-activate when targets, AoE templates, or automation modules (Midi-QOL) matter.' This tells the agent exactly when to use this tool versus the alternative, and also implies when not to use it. This is explicit and actionable.

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