Get Shipping Label

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

Annotations already declare readOnlyHint=true. The description adds minimal behavioral context beyond returning PDF data. It does not discuss potential size limits, timeouts, or authentication requirements, which would be helpful for a download tool.

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 exceptionally concise: two short sentences that directly convey purpose and output format. Every word adds value with no redundancy.

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 adequately covers the tool's action and output for a simple retrieval tool with one required parameter. It could mention that the label ID must exist, but overall it is sufficiently complete given the annotations and schema.

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% for the one parameter 'shippingLabelId', with a clear description in the schema. The tool description adds no extra meaning for the parameter beyond restating 'by its ID', so baseline 3 applies.

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 clearly states 'Download a shipping label by its ID', specifying the verb (download) and resource (shipping label). This distinguishes it from sibling tools like create_shipping_label and other get_* functions.

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 implies use when needing to retrieve an existing shipping label, but does not provide explicit guidance on when to avoid this tool (e.g., if the label needs to be created first) or mention alternatives like create_shipping_label.

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