vrc_export_fbx

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

No annotations are provided, so the description must disclose behavioral traits. It mentions axis conversion, disabling leaf bones, and applying correct scale, but does not cover file overwrite behavior, error handling, or other side effects.

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 with a front-loaded purpose and bullet-style parameter list. It uses minimal words, but the structure is clean and easy to parse.

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 and presence of an output schema, the description covers essential aspects: purpose, key operations, and parameter meanings. It lacks details on failure modes or file handling, but is mostly complete for a straightforward export tool.

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?

Parameter schema coverage is 0%, but the description lists each parameter with a brief explanation (e.g., filepath as full output path, apply_modifiers as apply before export). This adds meaning beyond the schema, which only provides titles and defaults.

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 it exports a model as FBX with VRChat-optimized settings, specifying axis conversion, leaf bones, and scale. This is a specific verb+resource that distinguishes it from generic export tools like io_export_fbx.

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 the tool is for VRChat-optimized exports, but does not explicitly state when to use it over alternatives like io_export_fbx. No exclusions or context on when not to use it are provided.

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