vrc_setup_contacts

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

Discloses that it only places bones and generates JSON, not adding Unity components, which sets accurate expectations. No annotations exist, so description carries full burden; it lacks disclosure of side effects like modifying existing bones.

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?

Concise, front-loaded purpose, followed by clear parameter list. No wasted sentences; every part is informative.

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 purpose, parameters, behavior, and output schema. Minor gap: doesn't specify coordinate space for bone placement (local vs world). Otherwise complete for a tool with good annotations and output 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?

With 0% schema coverage, the description provides thorough parameter explanations including examples and valid values for preset and custom_contacts, compensating fully for missing schema descriptions.

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 sets up VRChat Contact Senders and Receivers by creating marker bones and generating Unity configuration JSON, distinguishing it from sibling tools like vrc_setup_gestures or vrc_setup_physbone_chain.

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 on when to use this tool versus alternatives, such as unity_setup_contacts, nor prerequisites like requiring an armature. The description only details parameters without context for selection.

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