nozzle_wear_status

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

No annotations are provided, so the description must carry the full behavioral burden. It usefully discloses that the feature is Pro+ and requires Kiln Pro, but it does not explain whether the tool is read-only, what happens when the user lacks Pro, what data is returned, or how wear/maintenance predictions are represented.

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 purpose is front-loaded and the description is short. However, 'Pro+' and 'Requires Kiln Pro' are redundant, and the upgrade URL is promotional rather than operational, so not every sentence earns its place.

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 tool with two parameters, no output schema, and no annotations, the description is incomplete. It tells the agent the feature is gated but leaves parameter meaning, return contents, and failure behavior unspecified.

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 0%, so the description should compensate but largely does not. It implies a printer context via 'for a printer's nozzle', which loosely maps to printer_id, but it says nothing about the recent_filament parameter or how either parameter affects the wear analysis.

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 description states a specific resource and concept: accumulated wear status for a printer's nozzle. It is clearly about nozzle wear rather than general printer status. However, it does not distinguish this tool from closely related siblings such as get_my_nozzle_wear_patterns, nozzle_drift_attribution, maintenance_due, or get_nozzle_state.

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?

The only usage guidance is that it requires Kiln Pro. It gives no indication of when to use this tool instead of adjacent wear, maintenance, or nozzle-state tools, and no exclusions or alternatives are named.

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