Create dance module

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

Annotations only declare that this is a write operation (readOnlyHint=false, openWorldHint=false). The description adds meaningful behavioral context beyond that: the tool scaffolds from a template into a specific directory and the created module will not load until modules are reloaded or reanim.luau is re-run. It does not disclose overwrite/failure behavior for pre-existing files.

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?

Two sentences plus a short clause, front-loaded with the core action and destination, then prerequisites, then the post-creation step. Every sentence earns its place with no 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?

For an 8-parameter write tool with no output schema and full schema coverage, the description covers the action, artifact location, key input constraint, and the required follow-up load step. It omits nothing critical, though it could note the default no-overwrite behavior, which is left to the schema.

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%, so the baseline is 3. The description adds constraint semantics the schema lacks — that anim must reference an *existing* Content/Anims name (not an arbitrary filename) and that song is an optional .mp3 — clarifying the expected value domain beyond the schema's example format.

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 names a specific verb (scaffold/create), the exact artifact (a DANCE user module .lua), and its destination (UhhhhhhReanim/Modules/) sourced from a template. This distinguishes it cleanly from the sibling reanim_create_moveset, which produces a different artifact type.

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?

It gives real prerequisites — anim must be an existing Content/Anims name or a 'file@url' — plus a follow-up step (reload modules), which is implied usage context. However, it never states when to choose this over reanim_create_moveset or the other dance tools, and gives no exclusions.

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