unity_setup_physbones

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states that PhysBone components are added, but does not mention whether it overwrites existing data, required permissions, or error handling for invalid JSON. The JSON format example is helpful but insufficient.

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 concise, front-loaded with the purpose, and well-structured with bullet points and a JSON example. Every sentence provides necessary information 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?

Given the moderate complexity (3 parameters, JSON input) and the presence of an output schema, the description covers the main usage. However, it omits details like whether existing physbones are replaced and input validation, leaving some gaps.

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%, so the description must add meaning. It provides explanations for all three parameters: project_path, avatar_object, and a detailed format example for physbones_json. This adds significant value beyond the empty schema.

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 verb 'Add', the resource 'VRCPhysBone components', and the context 'to an avatar from a JSON blueprint'. This distinguishes it from siblings like 'vrc_setup_physbone_chain' which sets up a single chain, and 'vrc_physbone_config' which configures existing physbones.

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?

The description implies usage for batch setup via JSON but does not explicitly state when to use this tool versus alternatives such as 'vrc_setup_physbone_chain' or 'vrc_physbone_config'. No exclusions or prerequisites are mentioned.

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