explain_calibration_for_design

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

With no annotations, the description carries the full burden. It usefully discloses that the tool is gated behind a Kiln Pro subscription and that its output is an explanation (an informational read), but says nothing about what the explanation contains, whether the offsets are per-material/per-feature, or behavior when no calibration profile exists.

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 purpose is front-loaded, but roughly half the text is marketing copy and a tracking URL that does not help an agent decide or invoke. The plausible content is one sentence.

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?

A six-parameter tool with no annotations and no output schema needs the description to explain inputs and expected return shape. It explains neither, so an agent cannot tell what to pass or what it will get back beyond 'an explanation'.

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 reads as 100%, but the parameter descriptions are only 'Default: ""' placeholders, so the schema conveys essentially no semantics. The description never mentions material, design_id, printer_id, feature_class, recipe_version, or nominal_size_mm, leaving six inputs unexplained in both places.

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 first sentence states a specific verb and resource: a plain-English explanation of applied calibration offsets. It is distinguishable from siblings like assess_calibration_status or query_per_machine_offset, though the following sentences drift into upsell rather than reinforcing scope.

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 when-to-use guidance, no conditions for selecting this over assess_calibration_status, get_calibration_freshness, or classify_calibration_confidence. The only stated condition is a commercial one (requires Kiln Pro), not a task condition.

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