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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds the authorization requirement ('Requires items.write'), the narrow write scope (only that column on the existing defaults row), and the return value ('Returns the saved print_order'). It does not clarify why destructiveHint is true despite the narrow update, but it does not contradict it either.

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?

Front-loaded with the core action and permission requirement, followed by scope, exclusion, and trigger condition. The telegraphic phrasing ('print_order is barcode, row_order, sent, sku, or name') is slightly redundant with the schema but does not bloat the description.

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 single-parameter tool with no output schema, the description covers purpose, permission, exact write scope, precondition, and return value. An agent has everything needed to decide when to call it and what to expect.

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 coverage is 0%, so the description carries the burden. It repeats the five enum values (barcode, row_order, sent, sku, name) already visible in the schema but does not explain what the setting actually controls (label sort order) or how each value changes printed output, so the added meaning is limited.

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 verb+resource: saves the organization's print_order_default, updating one column on the existing defaults row rather than creating a row. This is clearly distinguished from the many other print-related siblings (print_labels, start_print_job, copy_print_profile) that do different things.

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?

Explicitly names the trigger condition and the calling tools: 'Call this after print_labels or start_print_job returns needs_preference.' It also states a negative ('Does not create a row'), which prevents misuse of the tool as a general row-creation call.

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