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

Annotations already indicate this is a mutating, non-idempotent operation, and the description matches that by saying it adds an item to inventory. It adds mild context by noting the item is added 'with its full data,' but does not reveal additional behaviors such as duplicate handling, permissions, or side effects. No contradiction with annotations.

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?

Two sentences with no filler. The primary purpose is front-loaded, and the identifier-routing guidance is compactly placed in the second sentence. Every part 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?

With 100% schema description coverage, a required actorId, and clear routing between uuid and packId+itemId, nothing essential is missing for correct invocation. No output schema exists, but return-value details are not necessary for an add operation of this simplicity.

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 baseline is 3. The description adds value by connecting uuid to specific sibling tools (dnd5e-compendium-filter-items, pf2e-compendium-filter-items, compendium-search) and packId+itemId to compendium-browse, giving an agent concrete guidance on where to obtain valid parameter values.

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 states a specific action and resource: adding an item (weapon, spell, feat, gear) from a compendium pack to an actor's inventory. It clearly distinguishes this from generic item-create by emphasizing the compendium source and from item-filtering tools by being an inventory mutation.

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 on how to use the tool, explaining that either a uuid or packId+itemId must be provided depending on which sibling tool returned the data. It does not explicitly state when not to use it or name alternative tools, so it falls short of a 5.

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