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

The description discloses behaviors beyond annotations: it auto-rigs, adds skeleton and skin weights, and renders the result inline in an interactive 3D viewer. Annotations indicate readOnlyHint=false, openWorldHint=true, etc., and the description does not contradict them. It adds useful context about the inline rendering.

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, front-loaded with the main purpose, and contains no unnecessary words. It is efficient and well-structured.

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 one input parameter and no output schema, the description is complete: it explains what the tool does, what input is needed, and what happens after processing (inline rendering). It also contextualizes the input as possibly from other tools.

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?

There is only one parameter (glb_url) with 100% schema description coverage. The tool description adds meaning by stating the URL likely comes from other tools, providing additional context beyond the schema's 'http(s) URL to the static GLB mesh to rig'.

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 that the tool auto-rigs a static 3D model (GLB) into an animation-ready model by adding a humanoid skeleton and skin weights. It also mentions providing a GLB URL, which aligns with the tool name 'rig_mesh'. However, it does not explicitly distinguish this tool from sibling tools like 'forge_avatar' or 'mesh_forge', though it hints at working with outputs from other tools.

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 gives explicit guidance on when to use: when you have a static GLB model and want to rig it for animation. It also suggests the GLB URL may come from other tools, providing context. However, it does not mention when not to use or name alternatives among the sibling tools, though the use case is clear.

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