sfc_get_label_url

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

No annotations are provided, so the description carries the burden. It does clarify that this is a non-side-effecting URL builder rather than a print trigger, which is genuinely useful, but it says nothing about auth requirements, whether the URL expires, or what the return value looks like.

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 action and followed by the key usage distinction. Every sentence earns its place with no filler.

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?

With four parameters at 25% coverage, no annotations, and no output schema, the description should explain the return shape (a URL string) and the meaning of isPrintDeclare/printType. It leaves those gaps open, so an agent cannot call this confidently beyond the required field.

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 only 25%: printType and isPrintDeclare have no schema descriptions, and the description adds nothing about them. Only orderCode ('confirmed') and printSize (via the schema) are covered, so the description fails to compensate for the low coverage.

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-plus-resource: build a label PDF URL for a confirmed orderCode. It distinguishes itself from a print action, but it doesn't differentiate against siblings like sfc_get_track or sfc_preview_order by name.

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 frames the when-to-use case (you only need the link) and implicitly the when-not case (don't call print). The 'confirmed' qualifier also hints at a prerequisite state, though no alternative tool is named and no prerequisite steps are spelled out.

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