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

It adds a useful behavioral detail beyond annotations: 'Always posts a card to chat.' However, it doesn't state whether the item's quantity is decremented or the item is destroyed, which is central to consuming an item. The annotations signal mutation via readOnlyHint=false, but the description could be more explicit about the mechanical effect.

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 and front-loaded: system restriction, action, itemId constraint, and chat side effect each earn their place. No filler or redundant elaboration.

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 three-parameter tool with no output schema and minimal annotations, the description covers the essentials: system, item type, lookup path, and a side effect. It omits explicit notes about quantity decrement or permission requirements, which prevents a perfect score.

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 itemId, actorId, and quantity. The description reinforces that itemId must be consumable and found via item-list, but this mostly repeats schema information rather than adding new parameter-level meaning.

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 opens with 'PF2e only' to scope the system, then names a specific action and resource: 'Use a consumable item (potion, scroll, etc.)'. The consumable constraint differentiates it from spell-casting or item-posting siblings like pf2e-cast-spell and pf2e-post-item.

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: PF2e only, itemId must be a consumable, and item-list is the source for finding one. It doesn't explicitly name alternative tools for non-consumable actions, but the consumable requirement is a clear exclusion criterion.

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