setBlocks

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 disclosing behavior. It indicates the operation modifies blocks but does not explain overwriting semantics, whether changes are applied atomically, what happens if the project is not active, or what the return value/error behavior is. For a mutation tool, this is a substantial gap.

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, direct sentence with no wasted words, and the core action is front-loaded. It is concise and easy to parse, though the content is thin.

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 that this is a batch mutation tool with no annotations, no output schema, and one complex parameter, the description does not provide enough context for reliable use. Missing details include coordinate system, block replacement behavior, failure semantics, and relationship to sibling block-placing tools.

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 only that multiple blocks are set. It does not explain the meaning of pos, block, id, or properties beyond their names. The schema provides structural shape but very little semantic guidance, and the description does not compensate.

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 states a clear action and resource: set multiple blocks in the active project. The plural 'blocks' and 'in one call' help distinguish it from the sibling setBlock, though it does not explicitly name alternatives.

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 this tool is for setting several blocks at once, which is useful context. However, it does not state when to prefer this over setBlock, fillBox, wall, or similar tools, nor does it provide any exclusions or prerequisites.

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