blender_vrm_metadata

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

The description makes broad claims ('Comprehensive', 'Handles all VRM-specific settings') without detailing any behavioral traits such as side effects, file writes, scene modifications, or required context. Annotations have all hints set to false, so there is no contradiction, but the description carries the full burden and fails to disclose specifics beyond the generic 'management' concept.

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 two sentences and brief, but the first sentence largely restates the tool name ('VRM metadata management') and the second adds platform context. It is not bloated, but the limited content could have been used more effectively to list the operation modes or key capabilities.

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 complexity with 13 parameters, 5 operation modes, and an output schema, the description is too sparse. It does not explain the different operations, how parameters interact, or what the output schema contains. An agent would need to inspect the schema carefully to understand the tool's capabilities, and the description does little to orient or guide that exploration.

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?

The input schema provides 100% coverage with detailed descriptions for all 13 parameters, including defaults and enums. The tool description adds no additional parameter information, so the baseline of 3 is appropriate. The description does not mislead or contradict the 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 states 'Comprehensive VRM metadata management for avatar configuration' which indicates the general domain but does not specify the actual operations (set first-person offset, blink viseme mappings, spring bones, look-at, export) that are shown in the schema. It is not a tautology, but the verb 'management' is broad and the description relies heavily on the schema to convey what the tool actually does.

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 no explicit guidance on when to use this tool versus other Blender tools. It mentions target platforms (VRChat, VRoid Studio) but gives no exclusions, alternatives, or context for choosing among the different operations. The agent is left to infer usage from the schema and enum values.

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