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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds that the item is added 'with its full data', which implies the compendium data is copied into the actor rather than referenced. It does not mention what happens on duplicate additions (non-idempotent) or permission requirements, so the added behavioral value is moderate.

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?

A single dense sentence that front-loads the action and resource, then lists the accepted identifier sources. No wasted preamble. It is a bit packed, but every clause (item types, uuid format, source tools) carries information.

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 tool has six parameters with full schema coverage and no output schema. The description covers the action, the accepted identifier formats, and the upstream tools that supply them, which is enough for an agent to invoke it correctly. It is slightly thin on mutation semantics (duplicate handling, permissions) given annotations cover only the basics.

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 six parameters in detail, including the uuid format and the uuid-replaces-packId+itemId relationship. The description reinforces the uuid format and the dual sourcing pattern, but adds no syntax or constraints beyond the schema. Baseline 3 applies.

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: 'Add an item ... from a compendium pack to an actor's inventory'. It also enumerates item types (weapon, spell, feat, gear), which helps an agent distinguish it from item-create (creating a fresh item). It does not explicitly contrast with the closest sibling item-create, but the compendium sourcing makes the distinction largely implicit.

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 names the upstream tools that produce the required identifiers (dnd5e-compendium-filter-items, pf2e-compendium-filter-items, compendium-search, compendium-browse), which is useful routing. However, it does not state when to prefer this over item-create or actor-create-from-compendium, nor any prerequisites or exclusions.

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