loot_generate

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

With no annotations provided, the description carries the full burden, and it does well by explaining the deterministic table-based output: all possible outcomes for the CR bracket, d100 range, probability percentage, and average coin amounts. It also clarifies that the tool returns a table for the user to roll against rather than performing a random roll itself.

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 efficient, front-loaded with the core purpose, and every sentence adds value: what the tool does, what it returns, and how to use the result. There is no filler or repetition.

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 one-parameter tool with no output schema, the description explains the input, the output categories, and the intended post-call action. It is sufficiently complete for an agent to select and invoke the tool correctly, though it could mention coin denominations explicitly.

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 covers 100% of parameter documentation with a detailed valid-value list for 'cr'. The description adds useful context about CR brackets and the relationship to treasure tables, but it does not need to compensate for schema gaps.

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 and resource: 'Generate individual treasure loot for a monster of a given Challenge Rating' based on the DMG individual treasure tables. It clearly distinguishes this tool from sibling tools, which are predominantly search/get operations or encounter/CR utilities.

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 clearly establishes when to use the tool: when generating individual treasure loot by a monster's Challenge Rating. It also gives practical usage instructions ('Roll a d100 to select a row, or use the average coins'), though it does not explicitly discuss exclusions or contrast with alternative tools.

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