vrc_setup_eye_tracking

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

No annotations are present, so the description must fully disclose behavioral traits. It only states that blend shapes are created and bones optionally created, but omits important details like whether existing blend shapes are overwritten, required mesh structure, or any side effects (e.g., modifying the armature). The agent lacks insight into the tool's operational behavior.

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 very concise: two short sentences for the purpose and two bullet points for parameters. It front-loads the core function and efficiently explains parameters 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?

The description covers the basic functionality but lacks mention of prerequisites (e.g., required mesh type, selection state), expected output (though an output schema exists), and error handling. For a setup tool, more contextual guidance would improve completeness.

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 description adds meaning beyond the input schema by explaining that mesh_name auto-detects when empty and that create_bones creates missing bones by default. This clarifies usage intent, though it could detail the auto-detection logic or what constitutes 'missing' bones.

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's purpose: 'Set up VRChat eye tracking: creates eye tracking blend shapes and optionally eye bones.' It specifies the verb (set up, creates) and resource (eye tracking blend shapes, eye bones), distinguishing it from sibling tools like ft_setup_eye_tracking_full which may have a broader scope.

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 guidance is provided on when to use this tool versus alternatives such as ft_setup_eye_tracking_full or other eye-related setup tools. There is no mention of prerequisites, context, or when not to use it.

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