compare_design_versions

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

No annotations exist, so the description carries the full behavioral burden. It does disclose a real behavioral fact not in the schema — that the feature is gated behind Kiln Pro — but it says nothing about what a comparison returns, whether it mutates state, or what happens for non-Pro callers beyond the upsell link.

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 first sentence is well-formed and front-loaded, but the remaining three lines are promotional copy ('branch, restyle, compare outcomes') and an upgrade URL. The gating note earns its place; the marketing sentence and link dilute rather than inform.

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?

For a four-parameter, no-output-schema, paywalled tool, the description should at minimum explain what the comparison yields and how the required version ids are obtained. Both are absent, leaving the agent unable to invoke it confidently even where the license exists.

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 coverage is only 50%, and the undeclared parameters are the important ones: version_id_a and version_id_b have no descriptions at all, while mesh_path_a/b only say 'Default: ""'. The description adds no meaning about what a version id is, how the two mesh paths relate to the version ids, or whether either is optional.

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 opening sentence states a specific verb and resource: comparing print outcomes between two named design versions. It is clear what the tool produces conceptually, but it never distinguishes itself from nearby siblings such as diff_design_versions or compare_mesh_versions, so an agent cannot tell which comparison tool to pick.

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 only usage signal is 'Requires Kiln Pro', which is a prerequisite, not guidance on when to choose this over alternatives. With diff_design_versions and compare_mesh_versions in the sibling list, the description gives no criteria for picking this one.

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