post-item-card

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

Details the Activity system, behavior for items without activities, auto-targeting degradation headless, and GM-only restriction. Lacks explicit mention of side effects or permissions beyond GM-only, but adds significant context beyond schema.

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?

Single paragraph, front-loaded with main purpose, no wasted words. Every sentence adds essential 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?

Covers main use cases, error condition (no activity), and headless behavior. No output schema exists, but description hints at return (clear reason or card). Minor gaps in error handling details, but sufficient for effective use.

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?

Each parameter's description adds value beyond the schema: explains action enum values (use/attack/damage), consume resource spending, activity selection, and critical option for damage. Schema coverage is 100%, but description enriches understanding.

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 it posts a rich dnd5e card with interactive buttons or rolls attack/damage, specifying the resource (actor's item/feature/spell) and distinguishing from plain cards via send-chat-message.

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?

Explicitly tells when to use this tool (for interactive buttons without a module) and when to use an alternative (send-chat-message for plain cards). Also notes GM-only restriction.

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