daz_set_emotion

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

Discloses morph priority order, error handling (no raise on missing morphs), and return structure. With no annotations, this is good but could mention if changes are reversible or require specific scene 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?

Compact, front-loaded purpose, organized into Args/Returns/Notes. Every sentence adds value without redundancy.

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?

Covers behavior and parameters well, but lacks prerequisites (e.g., character must exist) and doesn't note that output schema exists. Almost 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 has 0% coverage, but description fully defines each parameter: character_label, emotion (with 13 enumerated values), and intensity (default 0.7, 0–1 range).

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 applies an emotional expression via morphs and body adjustment, distinguishing it from generic property setters like daz_set_property or pose tools.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., setting morphs individually). The behavior description is present but not comparative.

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