get_printer_melt_rate

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

No annotations are provided. The description identifies the data source as the printer's own slicer / Kiln slicing, but it does not state read-only behavior explicitly, failure modes for unsupported printer-material combinations, or whether the lookup has side effects.

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 a single compact sentence with the metric front-loaded and no filler. The phrase 'the figure Kiln slices it at' is somewhat opaque, but the overall size is appropriate.

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 3-parameter lookup with no annotations and no output schema, key details are missing: units (mass vs volume), how nozzle_mm affects the result, and what happens for unsupported material/printer combinations. The description provides only a high-level metric definition.

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% for 3 parameters. The description mentions material and printer conceptually but does not explain printer_model, material, or the optional nozzle_mm parameter and its effect on melt rate, so it does not compensate for the undocumented schema.

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?

States a specific metric: how much plastic per second a printer's slicer allows a material to melt, tied to Kiln slicing. An agent can identify this as a melt-rate getter, though the wording is idiosyncratic and does not distinguish it from related material/print-setting tools.

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?

There is no explicit when-to-use guidance, prerequisites, or alternatives among siblings such as check_nozzle_capacity_for_print or get_material_slicing_profile. Usage is only implied by the tool name and metric description.

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