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

Annotations only say readOnlyHint=false, so the description carries the responsibility of explaining the side effect. It does so by saying the tool posts to chat and, importantly, guarantees the item is not consumed or cast. It also clarifies the prerequisite that itemId must come from item-list and belong to the actor. The only gap is that the behavior when showInChat=false is not disclosed.

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 short sentences with no filler. It front-loads the system requirement ('PF2e only'), states the core action, and immediately gives the critical constraint about not consuming or casting. Every sentence contributes useful guidance.

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 simple post-to-chat tool with 100% schema coverage and no output schema, the description is nearly complete: it states scope, item source, and the absence of consumption/casting. The main remaining gap is the unspecified behavior of showInChat=false, which prevents full completeness.

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 already covers all three parameters, but the description adds meaningful linkage: itemId must be an item on the provided actor and should be obtained from item-list. This helps prevent the common mistake of supplying a world item or an item from another actor. The semantics of showInChat=false remain under-specified, but the default true is clear.

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 uses a specific verb ('Post'), a specific resource ('any item's card to chat'), and defines what the card contains ('description, traits, actions'). It also distinguishes itself from related PF2e tools by explicitly stating it does so 'without consuming or casting it,' so an agent can tell it apart from pf2e-use-consumable and pf2e-cast-spell.

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, and the purpose is to share an item card rather than consume or cast the item. This implies when to use it versus related item-affecting tools, and it points to item-list as the source for itemId. It does not explicitly name sibling alternatives or state when not to use them, but the exclusion is clear enough.

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