blender_action_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does state that the tool creates a new action and may assign it to an object, but it does not disclose what happens if the object already has an action, whether the new action becomes the active one, or how omitted optional parameters are handled. These are significant gaps for a mutation tool.

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 a single front-loaded sentence with no filler. The core operation comes first, the helpful parenthetical defines the domain concept, and the optional assignment behavior is included without extra wording.

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 simple two-parameter creation tool with full schema coverage, the description is mostly adequate for basic invocation. However, with no output schema and no annotation context, it does not fully cover side effects of assignment, default behavior when name is omitted, or what the caller should expect as a result.

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 adds little beyond the schema: 'optionally assign to object' roughly mirrors the object_name parameter's role, but it does not clarify defaults or constraints beyond what the schema already states.

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 uses a specific verb ('Create'), identifies the resource ('action'), and clarifies the Blender-specific meaning with 'animation data container'. It also states the optional assignment behavior, which distinguishes it from tools like blender_action_list and keyframe 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 intended use is implied by 'Create a new action' and the optional assignment to an object, but there is no explicit guidance about when to use this tool versus alternatives, such as when to list existing actions with blender_action_list instead.

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