label

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

The description discloses the tool's operations (including print and download, which may have side effects) and the return format (JSON string). While annotations indicate no destructiveness, the description adds context about what each operation does, though it could clarify which operations modify state (e.g., printing triggers a print job).

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 concise and well-structured: it front-loads the purpose, then lists operations and their arguments in a clear bullet-style format. Every sentence adds value without redundancy.

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?

The description covers all parameters and operations, and the presence of an output schema means detailed return structure is handled elsewhere. However, it lacks handling of error cases or edge conditions (e.g., missing template_id for print operations).

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: operation (list of possible values), label_type (filter for list_templates), template_id (for print/download), item_ids (list of IDs), destination (file path). This adds critical meaning beyond the schema's titles.

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 clearly states the tool's purpose: 'Label printing and template management in InvenTree.' It enumerates the five specific operations (list_templates, print_part, etc.), making it distinct from sibling tools like barcode or report which handle different domains.

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 lists the available operations and their parameters, which guides usage within the tool. However, it does not explicitly state when to use this tool versus alternatives (e.g., barcode for barcode printing) or provide conditions for when not to use it.

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