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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds structural behavior the annotations cannot (the gun is a sibling under Hold, not the world-body hand bone) and lists outputs, but the phrase 'Pull Mixamo T-pose characters ... into bodies paths' reads like a write/import action that sits uneasily with readOnlyHint=true. This is ambiguous rather than a clear contradiction, so I score it as a moderate gap rather than flagging.

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?

Telegraphic and front-loaded: the core deliverable leads, followed by returned artifacts, prerequisite, structural constraint, and integration partner. Every clause carries information with no filler, though the fragmented phrasing is slightly harder to parse than flowing prose.

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?

With no output schema, the description usefully names the returned artifacts and the rig structure, and it discloses the input prerequisite and the companion tool. For a one-parameter kit generator this is nearly sufficient, missing only explicit sibling differentiation and any note on failure/edge conditions.

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 description coverage is 100% and the single 'prompt' parameter even carries an example ('fps', 'tactical bomb defusal'), so the schema fully documents the input. The description adds no syntax or format guidance beyond what the schema already provides, making the baseline 3 correct.

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+resource: builds a CS-style first-person arms + gun viewmodel under Camera3D/Hold and enumerates the artifacts it returns (viewmodel.json, gf_viewmodel.gd, clip shader). This distinguishes it from generic siblings like gripforge_generate_fp_hands, though it never explicitly contrasts itself with gripforge_fps_kit or gripforge_fp_hands_schema, so a reader must infer the boundary.

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?

'Pair with gripforge_input_kit' gives an integration hint, and the Mixamo T-pose (palms down) prerequisite tells the agent what inputs to prepare. However, there is no explicit when-to-use vs when-not guidance and no differentiation from the many adjacent FPS/hands tools, leaving selection largely to inference.

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