get_calibration_freshness

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

No annotations exist, so the description carries the full behavioral burden, and it discloses little: nothing about whether this is a read-only lookup, what shape the report takes, how "freshness" is computed, or whether there are rate/cost implications. The second sentence describes the value of Kiln Pro in general rather than the behavior of this call.

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 in sentence one and the Kiln Pro requirement is legitimately decision-relevant. But the middle sentence is product marketing and the trailing upgrade URL is pure upsell, neither of which helps 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?

With no annotations, no output schema, and half the parameters undocumented, the description would need to explain the return shape and the material parameter to be callable with confidence. It instead spends that space on tier promotion, leaving meaningful gaps for a two-parameter, gated tool.

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%: printer_id has no description and material is documented merely as 'Default: ""'. The description does not explain what material does or how it interacts with the phrase "every calibration combination," which could even suggest no filtering at all — so it fails to compensate for the coverage gap.

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 gives a specific verb and resource: "Report freshness for every calibration combination of a printer." The scope (all combinations for one printer) is clear, but the tool is not differentiated from nearby siblings such as assess_calibration_status, classify_calibration_confidence, or get_calibration_health_recommendations, and "freshness" is never defined as age, staleness, or measurement recency.

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" is a real gating prerequisite an agent needs before calling, which is more than nothing. However, there is no guidance on when to prefer this over assess_calibration_status or the other calibration siblings, and no statement of what the agent should do if the user lacks Kiln Pro beyond a pricing URL.

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