import-rolltable

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

Given no annotations, the description carries full burden. It discloses that embedded results with @UUID links come intact, that the tool is GM-only, and that it only works with premium-book packs. It doesn't mention if the import is additive or overwrites, but 'Copy' implies duplication. The description provides reasonable 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 extremely concise with three sentences that front-load the core action, then add context and constraints. Every sentence adds value, and there is no redundant 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?

The description explains why the tool is needed (world-only roll tables), what is copied (embedded results with UUIDs), and user restrictions (GM, premium packs). It lacks details on error handling or exact outcome, but for a simple import tool without output schema, it is sufficiently complete.

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 100%, so the schema already documents each parameter. The tool description does not add meaningful detail beyond what is in the schema. Baseline score of 3 is appropriate.

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 ('Copy a whole RollTable from a compendium pack into the world') and provides a concrete example (DMG treasure/magic-item table). It distinguishes from siblings like create-rolltable and roll-on-table by explaining the import necessity.

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 explains when to use this tool (before roll-on-table) and why (roll tables are world-only at roll time). It also specifies constraints: premium-book packs only (SRD refused) and GM-only. However, it does not explicitly compare to alternative tools like import-item or list-rolltables.

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