create-rolltable

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

With no annotations, the description details behavioral traits: SRD refs are refused, premium items render as @UUID links, ranges auto-assign, formula defaults to 1d<total weight>. It also notes GM-only. However, it misses potential side effects like permission requirements or overwrite behavior.

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 paragraph that packs essential information concisely. It is front-loaded but could benefit from more structured formatting like bullet points. It is effective without being overly verbose.

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 description covers purpose, parameters, and key behavior, but lacks information about the return value (e.g., what is returned after creation). Given no output schema, this is a gap. Otherwise, it is reasonably complete for the 7 parameters.

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 adds value by explaining how results combine text and uuid, the auto-assignment of ranges, and the default formula. This goes beyond the schema descriptions, earning a 4.

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 creates a RollTable from a list of results, specifies the types of results (text/UUID), mentions auto-assignment of ranges and formula, and distinguishes it from siblings like import-rolltable and roll-on-table.

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 says 'Use for random encounter/loot/rumour/treasure tables. GM-only.' It provides clear use cases and access restrictions, but does not explicitly mention when not to use or alternatives beyond the implicit context.

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