blender_rigging

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

Annotations are all false, so the description carries the burden. It discloses the portmanteau design and lists operation names, but does not mention that operations are selected via the 'operation' parameter, nor describe side effects like scene modification or irreversibility (e.g., manage_vertex_groups can remove groups, reset_pose clears transformations). The description focuses on what operations exist, not how the tool behaves.

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 well-structured with clear categories, but the opening 'PORTMANTEAU PATTERN RATIONALE' paragraph is largely meta-commentary that does not aid invocation. The bullet lists are useful but partially duplicate the schema's operation enum. It earns a middle score due to organization but is padded with non-essential rationale.

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 complexity (25 parameters, 11 operations), the description provides a high-level overview and grouping but fails to explain that exactly one operation is executed per call based on the 'operation' parameter, or that parameters are conditional per operation. The output schema exists but is not shown, so the description carries some burden. It is adequate but leaves practical usage flow implicit.

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%, so the baseline is 3. The description's categorization of operations helps associate parameters with operations, but it does not add parameter-specific meaning beyond the schema. The parameter descriptions in the schema already cover usage details, so the description neither compensates nor detracts significantly.

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 identifies the tool as a 'Complete character rigging system for Blender' and enumerates all 11 operations across five categories. This gives a specific verb (rigging), resource (Blender armatures/bones), and distinguishes it from any sibling tool since no other rigging-specific tool is listed.

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 usage when character rigging is needed and lists operations grouped by workflow stage, but it does not provide explicit when-to-use vs alternatives or exclusions. It lacks statements like 'For animation keyframing, use blender_animation instead.' The rationale about preventing tool explosion gives context but no actionable guidance.

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