fleet_nozzle_agreement

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that Kiln Business is required, but does not explain whether the operation is read-only, how disagreement is determined, what 'matter first' means, or what the response contains.

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 description is short but poorly structured: it opens with an awkward question, then spends two lines on tier marketing and an upgrade URL. The promotional content does not help an agent select or invoke the tool.

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 no annotations and no output schema, the description should explain the parameter, return shape, and read/comparison behavior. It instead focuses on Business-tier upsell text, leaving essential invocation context missing.

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?

The sole parameter, printer_names, has 0% schema description coverage, and the description does not explain its semantics. It does not say whether it is an optional filter, whether names or IDs are expected, or what happens when it is omitted.

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 conveys the resource and comparison being performed: registered machines that disagree with Kiln's nozzle record, with prioritization. However, it is phrased as a question rather than a clear tool action, and it does not distinguish this from nearby nozzle/fleet tools such as list_nozzle_states or nozzle_drift_attribution.

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 description provides no guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. It only states a Business-tier requirement, which is an availability constraint rather than usage guidance.

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