Compare a current Zadig build against a desired build payload to spot differences, helping ensure the build matches your intended configuration.
Diff current Zadig build detail against desired build payload.
| Name | Required | Description | Default |
|---|---|---|---|
| build | Yes | ||
| build_name | Yes | ||
| project_key | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does 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 side effects and behavioral traits. It communicates the comparison operation, but it does not explicitly state that the tool is read-only, whether it fetches the current build from the system, how mismatches are handled, or any permission or error conditions.
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?
A single front-loaded sentence with no filler. Every word contributes to the operation and does not waste the agent's attention.
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?
The presence of an output schema helps, but for a tool with 0% parameter schema coverage, an unconstrained nested 'build' object, and no annotation coverage, this description is too thin. It leaves an agent uncertain about required input semantics beyond build_name/build and when to invoke this tool versus the many build-related siblings.
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%, so the description must compensate. It loosely maps 'desired build payload' to the build object and 'current build detail' to the build_name lookup, but it does not explain project_key or clarify the expected structure of the 'build' object, which is especially important given additionalProperties is true.
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 ('Diff') and resource ('current Zadig build detail' vs 'desired build payload'), which clearly identifies the operation. It is distinguishable from sibling diff tools because it names 'build' as the resource, though it does not explicitly contrast with workflow_diff, environment_diff, or template_diff.
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 a comparison use case: comparing an existing build detail to a desired payload, likely before applying changes. However, it never states when to prefer this over alternatives like zadig_build_get, zadig_build_apply, or other diff tools, nor does it mention exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.