blender_object_apply_transform

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds that it 'resets object transforms to default values' and 'applies transform data to the mesh data,' which is a key behavioral trait not fully covered by annotations. No contradictions.

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 concise, consisting of two short paragraphs and a docstring-style Args/Returns section. It front-loads the primary purpose and includes only essential information.

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 tool's moderate complexity, the presence of annotations and output schema, the description adequately covers purpose and effect. However, it omits details about what exactly 'apply transform' means in Blender (e.g., baking into mesh), which is minor.

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 input schema provides descriptions for each property (name, scale, location, rotation), so the schema already documents parameters. The description only mentions 'Object name and transform types to apply' without adding meaningfully beyond the schema. With low schema description coverage, the description does not compensate 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 states it applies object transforms (location, rotation, scale) to mesh data and resets object transforms. This distinguishes it from sibling tools like blender_object_transform (which sets transforms without applying) and blender_object_set_origin.

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 for applying transforms to mesh data but does not provide explicit guidance on when to use this tool versus alternatives like blender_object_transform or blender_object_set_origin. No exclusions or context are given.

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