VNyan bones

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

Despite no annotations, the description transparently discloses that reading a bone after overriding shows the pre-override value, and it mentions the source (plugin, live, read+write). This adds significant behavioral context beyond the schema.

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?

Two sentences plus a note; front-loaded with the main purpose. Could be slightly more structured by separating read and write operations, but overall concise and 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?

No output schema, so description should clarify return values for 'get' action (e.g., returns position/rotation). It mentions reading position/rotation but doesn't specify format. Also doesn't describe response for set/clear. Adequate for a simple tool but missing some return details.

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 100% with descriptions for all 5 parameters. The description adds extra context: Euler degrees, bone name format, and a reference to vnyan_guide for full list. It goes beyond the schema by explaining the override behavior related to set/clear actions.

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 specifies the tool reads bone position/rotation or sets/clears rotation overrides using HumanBodyBones names. It distinguishes from sibling tools like vnyan_blendshape or vnyan_param by focusing on bone operations.

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?

Describes when to read vs set/clear and explains a behavioral nuance (reading shows pre-override value). However, it does not explicitly compare to sibling tools or state when not to use this tool.

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