rig.create_control

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

Annotations (readOnlyHint=false, destructiveHint=false) rule out a simple read-only classification but do not establish what the tool actually does. The description adds only 'Risk: standard; maturity: L3' and a generic requirement note, neither of which discloses the operation's behavioral traits, side effects, or auth specifics.

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 text is short, but the first sentence merely restates the tool name and the other two sentences are generic boilerplate. No sentence earns its place by explaining function or usage, so this is under-specification rather than useful conciseness.

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?

Despite an output schema and eight parameters, the description gives agents no functional understanding of `rig.create_control`. It is impossible to predict what the command will create, how it interacts with the scene, or what conditions must be satisfied, making the definition materially incomplete for correct invocation.

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 adds nothing about the parameters. Schema coverage is about 63%, leaving `name`, `size`, and `_expectedSceneRevision` without descriptions, and the `shape` parameter explicitly defers details to command validation. The description does not compensate for these gaps, so an agent must guess the semantics of key inputs.

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.create_control`) and adds meta-level risk/maturity labels. It never states what the tool does, what a 'control' is, or what effect the command has in Blender. It is essentially a tautology plus boilerplate rather than a purpose statement.

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?

There is no guidance on when to use this tool, what conditions warrant it, or which sibling tools are alternatives. With many rigging siblings such as rig_bind, rig_create_armature, and rig_inspect, an agent gets no signal about where this tool fits.

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