request_calibration_test_print

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

With no annotations, the description carries the full burden. It does add real behavioral context: the call returns a pointer rather than performing calibration, and it is gated behind a Kiln Pro entitlement. It does not say what the pointer looks like (URL, token, expiry), what happens when the user is not Pro, or whether any state changes on the printer.

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 core sentence is well front-loaded. The second and third sentences are marketing/entitlement framing, and the upgrade URL with agent-tracking query params is pure upsell that does not help an agent invoke the tool correctly.

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?

No output schema, no annotations, two undocumented required parameters, and no statement of what the returned pointer is or how to consume it. For a 3-parameter tool with this much structured-data silence, the description leaves significant gaps an agent must guess at.

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 33%: only test_piece_kind has any documentation (default 'slicer_native'), while printer_id and material are bare strings with no enum or format. The description supplies zero parameter meaning, so it fails to compensate for the coverage gap on two required params.

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: returning a pointer to the slicer's native calibration wizard, which is distinct from actually running a calibration. However, it never names or contrasts itself with the obvious siblings (run_calibrate, calibrate_direct), so the agent must infer the difference. The second sentence muddies the purpose by describing what Kiln Pro 'would' do rather than what this call returns.

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?

'Requires Kiln Pro' plus 'when a design needs exact dimensions' implies a use condition and a prerequisite. But there are no explicit when-to-use/when-not rules and no mention of the many calibration siblings (run_calibrate, calibrate_direct, assess_calibration_status), so the agent has no guidance on choosing among them.

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