ddb_roll_treasure

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

Annotations already mark this as read-only and open-world, so the bar for additional context is lower. The description adds valuable behavioral details: fuzzy name matching for monsters, CR resolution, and how treasure_type affects the roll logic. No contradictions with annotations.

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 concise, front-loaded with the core purpose, and avoids redundancy. It packs key behavioral distinctions into two sentences without unnecessary filler.

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?

The tool lacks an output schema, and the description does not mention the return format or structure of the generated treasure. For a generator, knowing what the result looks like would be helpful. However, the tool's complexity is well covered, so this is a moderate gap.

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 coverage is 100%, but the description enhances parameter understanding by explaining the interplay between cr/monsters and treasure_type, the fuzzy matching behavior, and the character_level requirement for hoards. This goes beyond schema definitions.

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 tool generates treasure rewards using the 2024 XDMG tables, with specific behaviors for hoard vs individual. It is distinct from sibling tools, which are mostly search/get operations, by identifying itself as a generator.

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 clear guidance on when to use the tool and how to switch modes (CR vs monsters, hoard vs individual). It does not explicitly mention alternatives or exclusions, but the usage context is well-defined.

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