get_my_nozzle_wear_patterns

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

No annotations exist, so the description carries the full burden. It does disclose the entitlement gate and the upgrade path, which is genuinely useful behavioral information, but it never states what the tool returns when the user is not on Pro (error, empty result, or upsell payload) or what the output matrix looks like.

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 one-line summary is front-loaded and clear, but the middle sentence is hypothetical marketing prose ('would track... attribute quality drift... predict maintenance') that describes a roadmap rather than the tool, and the bare URL line is bulky. The essential facts (what it is, Pro required) could be stated in half the space.

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 two-optional-parameter read tool with no output schema, the description covers the key gating fact but omits the failure mode for non-Pro users and the shape of the returned comparison data. Given the sibling overlap, an agent still cannot confidently choose this over nozzle_wear_status.

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 description coverage is 100% for the two parameters (limit, printer_id), so the schema does the work and the baseline of 3 applies. The description adds no meaning about what limit counts (rows? printers?) or how printer_id scopes the matrix to a single machine.

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?

It names the resource ('personal nozzle wear-rate matrix vs the population') and the differentiation angle (personal vs population), which is a real verb-free but specific claim. However the second sentence shifts to hypothetical phrasing ('Kiln Pro would track...') so it's unclear whether this tool actually returns a matrix or is merely a gated stub that returns an upgrade prompt. It also does not distinguish itself from sibling nozzle_wear_status, nozzle_drift_attribution, or get_community_wear_baseline.

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 an explicit precondition the agent needs, which is more than most tools offer. But there is no statement of when to use this versus nozzle_wear_status / nozzle_drift_attribution / get_community_wear_baseline, all of which overlap heavily with this topic.

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