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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral note that large labels may be truncated in JSON, but says nothing about auth, size limits, or when each format is returned.

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?

Two short sentences, front-loaded with the core action and with zero filler. The truncation caveat is appended compactly rather than buried in prose.

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 two-parameter read tool with annotations covering safety, this is nearly adequate. However, with no output schema, the description should explain what the returned bytes look like (base64 string, truncation behavior, format selection), and the format ambiguity is left unaddressed.

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 100%, so labelId and intentId are documented in the schema and the baseline is 3. The description adds no meaning for either parameter and instead introduces output formats that have no corresponding parameter, which may confuse an agent looking for a format switch.

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 action and resource: re-creating label bytes for download, with the output formats (PDF, ZPL base64) named. It is clearly distinct from lookup tools like GetLabel/FindLabel, though no sibling is named explicitly.

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 guidance on when to use this instead of GetLabel, FindLabel, RemakeLabel, or SendLabelToPrintNode. The only usage-adjacent content is the truncation caveat, which tells an agent about limits rather than about selection.

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