blockbench_apply_model

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

No annotations are provided, so the description carries full burden. It mentions 'atomically' but does not explain what atomicity entails (e.g., rollback on failure). No disclosure of destructive behavior (mode 'replace' overwrites) or error handling, rate limits, or state changes.

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 sentence that conveys the primary function without redundancy. While it is dense, it remains brief and front-loaded. However, it could be slightly split for readability.

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 complexity (7 params, deeply nested objects, no output schema, no annotations), the description is insufficient. It does not explain mode semantics, atomicity guarantees, how to structure input for common tasks, or what happens on conflict. The agent lacks context 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?

Schema description coverage is 0% and the description adds no parameter-level explanations. It lists component types but does not clarify how 'mode' works, the relationship between 'cubes' and 'groups', or which fields are mandatory beyond the schema. The agent must infer everything from the schema alone.

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 the tool creates or appends a Blockbench model from specific components like groups, cubes, UVs, textures, etc. It uses a specific verb ('apply model') and resource, and distinguishes from siblings such as blockbench_patch_model and blockbench_create_rig.

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 on when to use this tool versus alternatives like blockbench_patch_model for partial updates or blockbench_create_rig for skeleton creation. No mention of prerequisites or decision criteria for 'replace' vs 'append' mode.

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