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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description only needs to add context. It does add that this hits an external service (PrintNode) and uses the default printer, but it never explains the destructive nature — e.g., that a re-send may produce a duplicate physical label or incur cost, and whether it can be undone.

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?

A single, front-loaded sentence with no filler. The action, the target system, and the printer selection are all in the first clause set, and nothing is repeated from the title.

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 tool with full schema coverage and annotations, the description covers the core action. It is still thin on outcome: no indication of what 'sent' means (queued vs printed), what happens if the label was cancelled or already printed, or how failures surface. No output schema exists to carry that burden.

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 100% and both parameters are already documented ('Label usage id', 'Optional correlation ID for an existing investigation'). The description only indirectly clarifies that labelId refers to an existing label via 'again', so baseline 3 applies. Nothing is added about whether intentId is needed for tracing.

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 gives a specific verb and resource ('Send a label print job to PrintNode') and adds two distinguishing details: it is a re-send ('again') and it targets the organisation default printer. This separates it from DownloadLabel or RemakeLabel, though the relationship to those siblings is never stated 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?

The word 'again' implies the label already exists and this re-triggers printing, which is implied usage guidance. However, there is no explicit statement of when to prefer this over RemakeLabel, DownloadLabel, or GetLabel, and no prerequisites (e.g., label must already be created or in a printable state) are given.

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