vrc_create_humanoid_armature

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

No annotations exist, so description carries full burden. It mentions creation of armature but lacks details on side effects (e.g., overwriting existing armatures), required permissions, or reversibility.

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?

Extremely concise: two sentences plus a parameter list. Front-loaded with the core purpose, no wasted words.

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 tool's simplicity (creating a standard armature) and presence of an output schema, the description adequately covers intent. Could mention that it returns a reference to the new armature object, but not strictly necessary.

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?

Input schema has 0% description coverage, but the description lists all 4 parameters with defaults and brief explanations, adding significant meaning beyond the schema. Could be slightly more detailed (e.g., what 'include_fingers' entails).

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 it creates a VRChat-compatible humanoid armature from scratch with a T-pose skeleton. This specific verb+resource combination distinguishes it from siblings like 'armature_create' and 'vrc_rename_bones'.

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?

Implies usage when a new armature is needed, but no explicit guidance on when not to use or alternatives. Among many armature-related siblings, no comparison or exclusion criteria provided.

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