unity_setup_avatar_descriptor

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

No annotations are provided, so the description carries the full burden. It mentions adding a component and configuring defaults but does not disclose side effects like overwriting existing descriptors, required GameObject hierarchy, or error conditions. Adequate but not comprehensive.

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?

Description is concise with a clear structure: a brief purpose statement followed by a parameter list. Each sentence is informative and avoids 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?

Given 5 parameters and no output schema shown (though context indicates it exists), the description covers the essential setup details. However, it lacks information about return values or success/failure indications. Still, it is mostly complete for a setup tool.

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 0%, but the description provides detailed explanations for all 5 parameters, including defaults and acceptable values (e.g., view_position defaults to '0,1.6,0.3', lip_sync_style options). This significantly adds value beyond the schema alone.

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?

Description clearly states the tool adds VRC_AvatarDescriptor to a GameObject and configures viewpoint, lip sync, and eye tracking defaults. It distinguishes from sibling tools like unity_setup_contacts or unity_setup_expression_menu by specifying the exact component.

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?

Description implies usage for initial avatar setup but does not explicitly state when to use this tool versus alternatives. Given siblings like vrc_setup_visemes and unity_setup_physbones, the description could provide more guidance on when to choose this tool.

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