generate_loot

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

No annotations are provided, so the description carries the full burden. It states the tool generates loot, implying a write operation, but doesn't disclose behavioral traits such as whether it modifies existing data, requires specific permissions, has side effects (e.g., updating inventory), or what the output looks like (e.g., item list, loot table). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, target, and key parameters, making it appropriately sized for the tool's complexity.

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?

Given the tool has 4 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It covers the purpose but lacks details on behavior, parameter meanings, usage context, and expected results. For a tool that likely generates items or loot data, this leaves critical gaps for an agent to understand how to invoke it correctly.

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 0%, so the schema provides no parameter details. The description mentions 'creature type and CR', which maps to two of the four parameters, but doesn't explain 'corpseId' or 'sessionId', nor does it provide meaning for the mentioned parameters (e.g., what CR values are valid, examples of creature types). With low coverage, the description fails to compensate adequately.

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 the action ('Generate loot') and target ('for a corpse'), specifying it's based on 'creature type and CR'. It distinguishes from sibling tools like 'loot_corpse' or 'harvest_corpse' by focusing on generation rather than direct looting or harvesting. However, it doesn't explicitly differentiate from 'create_loot_table', which might be a related sibling.

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 provides no guidance on when to use this tool versus alternatives like 'loot_corpse', 'harvest_corpse', or 'create_loot_table'. It mentions the parameters but doesn't specify prerequisites, context (e.g., after combat, for DM planning), or exclusions. This leaves the agent with minimal usage direction.

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