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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses authentication requirements, upfront quota charging per row, non-refundable failed rows, plan-based row caps, and the asynchronous nature of the job via bulk_status.

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?

Every sentence earns its place: purpose, input shape, auth requirement, quota/cost warning, row cap, and return behavior. The critical operational warnings are included without fluff, and the core purpose is front-loaded.

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?

Despite having no output schema, the description tells the caller exactly what to expect (job id) and how to follow up (bulk_status). It also covers plan restrictions, quota semantics, and failure costs, making it complete enough for an agent to invoke the tool with appropriate expectations.

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 the schema already documents all six parameters. The description adds some framing, such as 'one object per label' and the {{variable}} placeholder pattern, but it does not significantly deepen semantic understanding of dpmm, output, width_in, or height_in beyond the schema.

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 names a specific verb and resource: 'Submit a bulk label production job' with one ZPL template and data rows, one object per label. It also distinguishes itself from the sibling status tool by noting it returns a job id and directing the user to bulk_status for checking completion.

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 clearly establishes the context for use: bulk jobs with a ZPL template and per-label data rows, plus a hard prerequisite that the API key's plan must include bulk jobs. It does not explicitly say when not to use this tool or name alternatives beyond bulk_status, so the exclusion guidance is not fully explicit.

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