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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the agent knows this is a risky mutation. The description adds field-level scope by naming the settings that can change, but it does not explain effects on future labels, reversibility, permissions, or partial-update behavior.

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, front-loaded sentence with no filler. The dense list of fields is efficient, though slightly compressed rather than optimally structured for scanability.

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 lists the changeable settings and annotations cover the destructive/non-idempotent profile, but there is no output schema and no explanation of partial updates, persistence, or how changes affect label generation. It is minimally adequate but leaves notable contextual gaps for a 7-parameter mutation tool.

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 71%, and the description names all seven updatable fields, helping map some parameters like packing_list and logo_on_label that lack schema descriptions. However, it adds no meaning beyond field names and does not clarify enum values or defaults.

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 uses a specific mutation verb ('Changes') and names the exact label settings affected (size, format, packing list, logo, QR codes, address correction, export format). It is clear what the tool does, though it does not explicitly distinguish the write operation from the read-only sibling get_label_settings.

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 gives no guidance on when to use this tool versus get_label_settings or other label-related siblings, and no exclusions or prerequisites are stated. It merely lists updatable fields, leaving usage decisions to inference.

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