label

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

Annotations indicate readOnlyHint=false, openWorldHint=true, destructiveHint=false, but the description does not elaborate on side effects, idempotency, or retry safety. It only mentions 'printing' without clarifying if it triggers external actions (e.g., printer).

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 front-loaded with purpose. The bullet-style Args and Returns sections are well-structured, though it could be slightly more compact without losing clarity.

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 operations and parameters adequately given the presence of an output schema and no nested objects. However, it lacks details on the behavior of each operation (e.g., what happens on failure) and prerequisites.

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 'Args' section adds meaningful explanations for all five parameters beyond the schema titles and types, such as 'label_type: Filter for list_templates (part, stock, location).' This compensates for the 0% schema description coverage.

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 lists specific operations (list_templates, print_part, print_stock, print_location, download_template), which distinguishes it from sibling tools like report or barcode.

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 implies usage through listed operations but does not explicitly state when to use this tool versus alternatives (e.g., report tool for reporting) or provide exclusions. No guidance on 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.