assess_calibration_status

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

No annotations, so the description carries the full load. It does disclose one genuinely valuable behavioral fact — the tool requires Kiln Pro (with an upgrade URL) — which tells the agent to expect a gating failure on free tiers. But it says nothing about whether the call is read-only, whether 'auto-import' mutates anything, what output form the confidence assessment takes, or what happens if the printer has no calibration data.

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?

One useful sentence followed by a marketing paragraph and an upgrade URL with tracking parameters. Roughly half the text is promotional and does not help an agent decide or call correctly; the payload is not front-loaded relative to its bulk.

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 4-parameter tool with no annotations, no output schema, 25% schema coverage, and no parameter or return-value explanation. The only substantive fact added (Kiln Pro gating) is insufficient for an agent to invoke the tool confidently.

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?

Four parameters and only 25% schema description coverage (mode's description is literally 'Default: "auto"'). The description never mentions mode, brief, printer_id, or intended_material, so neither schema nor prose explains what these are for — and the description must compensate here but does not.

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 line ('Calibration confidence + auto-import for slicer profiles') does name a resource — calibration confidence for slicer profiles — but bundles in an unrelated-sounding 'auto-import' capability that is never explained, and never distinguishes this from the many calibration siblings (classify_calibration_confidence, get_calibration_freshness, assess_calibration_status's near-namesakes). The bulk of the text is a Kiln Pro pitch rather than a statement of what the tool returns or does.

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 at all: no mention of prerequisites beyond the paywall, no differentiation from classify_calibration_confidence, get_calibration_freshness, explain_calibration_for_design, or any other calibration tool. An agent has to guess which of a dozen calibration siblings answers a given question.

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