gltf_to_r3f

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

Annotations already declare the safe read profile (readOnlyHint, idempotentHint, non-destructive), so the bar is lower. The description adds genuinely useful context beyond them: the output is generated source code destined for project files, not runtime scene state, which tells the agent the result is consumed differently from sibling inspect tools.

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 short sentences with the crucial output-destination constraint front-loaded before the core purpose. No padding, and the gltfjsx reference compresses an entire behavior into two 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?

For a code-generation tool with no output schema, the description covers what is produced and where it goes, which is what an agent needs to route the result correctly. It could say slightly more about the shape of the emitted component (props, exports), but nothing critical is missing.

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 and defaults for filePath, preload, and typescript already in the schema. The description adds no parameter detail beyond that, so the baseline 3 applies.

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?

States a specific verb ('Convert') and resource ('GLB/glTF file into a React Three Fiber component'), and reinforces it with the recognizable analogue '(like gltfjsx)'. This clearly distinguishes it from every sibling, which are all scene inspection/mutation tools rather than code generators.

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 '[FOR CODE]' tag and the note that output is meant to be written into project source files imply the context in which this tool belongs. However, it never states when to reach for it versus an alternative (e.g. scene_export) or any prerequisite; usage is only implied.

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