Surprise me

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

Annotations declare readOnlyHint=false, so the agent knows this is a mutating, closed-world call, but the description does not say what actually changes: whether the current dance and theme are overwritten, whether it applies or merely previews the combo, or whether prior settings are recoverable. For a 'surprise me' action tool that likely clobbers current state, this ambiguity is a real gap. No annotation contradiction, but little added behavior context.

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?

A single front-loaded sentence with no filler or repetition. It is appropriately sized for a no-argument action, though it is terse enough that it could have absorbed one clarifying clause without becoming bloated.

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 mutating tool with no output schema, the description leaves the main agent questions unanswered: whether the combo is applied permanently, what happens to existing dance/theme state, and where the results are surfaced. The annotations cover the safety profile but the description does not finish the job.

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 tool takes zero parameters and the schema coverage is 100%, so there is nothing for the description to compensate for. Baseline for a no-param tool applies.

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 concrete composite action: a random dance plus a random theme preset, with live snippets. The word 'combo' usefully differentiates it from the sibling reanim_random_dance and reanim_random_moveset, which each randomize only one thing. It stops short of stating that sibling relationship explicitly, so it is clear but not maximally differentiated.

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?

There is no when-to-use guidance at all. An agent cannot tell from the description when to pick this over the simpler reanim_random_dance, reanim_random_moveset, or the manual reanim_apply_theme_preset path. No prerequisites, no exclusions, no alternatives are mentioned.

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