render.configure_passes

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

Annotations provide readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false, but the description contributes zero behavioral context. It does not disclose what changes occur, whether the operation is safe, or what side effects to expect. The description is silent on behavior, so it adds no value beyond the annotations.

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 short, but it is under-specification rather than conciseness. The single sentence provides no actionable information, so it does not earn its place. It is comparable to the 'Process' example, which scored 2 for being merely a label.

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?

This tool has 6 parameters, an output schema, and annotations, but the description supplies none of the needed context. An agent cannot determine what the tool does, which parameters are required, or how to invoke it correctly. The definition is completely inadequate for a non-trivial rendering configuration command.

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 50%, with only internal fields (_requestId, _authorization, _transactionId) documented. The core parameter `passes` and `viewLayer` are undocumented. The description does not mention any parameters or explain their purpose, leaving the agent without essential meaning for the most important input.

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 is essentially a tautology: it states 'PartMe Blender Harness command `render.configure_passes`' without any verb or resource, and it does not explain what configuring passes actually does. No mention of render passes, view layers, or any Blender functionality, making it indistinguishable from the tool name.

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 versus alternatives. The only additional sentence about 'Per-request argument checks and session policy still apply' concerns procedural requirements, not usage context. No exclusions, no conditions, no references to sibling tools.

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