rig.bind

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

The description provides no behavioral information. Annotations are all false (not read-only, not idempotent, not destructive), but the description adds nothing about side effects, required scene state, or what the operation does. The risk and maturity notes are not behavioral transparency.

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 extremely brief but under-specified. It is not bloated, but it lacks substantive content. A single sentence that only names the command is not 'concise' in a helpful sense; it is an empty placeholder.

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 that binds a rig, the description is completely inadequate. It does not explain what the bind operation entails, what the expected inputs (armature, mesh) are, or what the output looks like. Even with an output schema present, the description fails to provide any operational context.

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?

The description does not explain any parameters. The schema has descriptions for the generic harness fields (_requestId, _authorization, _transactionId) but not for mesh or armature. With 50% schema coverage, the description should clarify these core parameters, but it does not.

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 only restates the command name 'rig.bind' and adds metadata about risk and maturity. It does not state what the tool does (e.g., bind a mesh to an armature), nor does it differentiate from siblings like blender_rig_create_armature or blender_rig_assign_weights. It is essentially a tautology.

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?

No guidance is given on when to use this tool versus alternatives. The mention of 'Per-request argument checks and session policy still apply' is generic and not about usage context. There is no discussion of prerequisites, typical workflow, or when to choose this over other rig tools.

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