VNyan blendshapes

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

Without annotations, the description carries the full burden. It discloses that overrides take priority over tracking, that values are live, and specifies the source as a plugin. However, it does not detail side effects like persistence or interaction with tracking when overrides are active.

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 relatively short (two sentences) and front-loads the essential actions (read, set/clear) and source. It could be slightly more organized but is efficient for its length.

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?

For a tool with 4 parameters and no output schema or annotations, the description covers core functionality but omits details about the difference between setOverride and setMeshOverride, and the exact behavior of clearing vs setting 0. It is adequate but leaves some questions open.

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%, so baseline 3. The description adds context about the value range (0-100) and that setting 0 removes the override, which aligns with schema but does not significantly deepen understanding beyond what the schema already provides.

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 reads blendshape values and sets/clears override values, and mentions it uses the same mechanism as the Blendshape node. This distinguishes it from sibling tools focused on other aspects like avatar, parameters, or 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?

The description provides general usage context (live, read+write) but does not explicitly specify when to use this tool over alternatives or when not to use it. The mention of 'same mechanism as the Blendshape node' offers implicit guidance for users familiar with VNyan.

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