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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds a genuine behavioral trait beyond that: it discloses it embeds current rates read in real time (「內含現行費率（即時讀取）與計費規則」), which tells the agent the payload is live data rather than a static document.

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?

Front-loads the core purpose and scopes content in one dense sentence, then adds rates and usage-fit. It is slightly heavy with the long stage enumeration, but every clause earns its place and no sentence is 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 an output schema present, return-value detail is unnecessary, and the description fully covers scope, content, and intended questions. It could go one step further by explicitly contrasting itself with sibling tools like lucky_about or lucky_freight_quote, but for a zero-parameter read tool it is essentially complete.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing parameter-side for the description to clarify, and it does not waste space inventing parameter semantics.

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 (取得/get) and resource (the complete China→Taiwan consolidation shipping workflow) and enumerates the exact stages covered: registration, warehouse address, ordering, pre-declaration, warehousing, consolidation, sea-express, customs, delivery. This makes it immediately distinguishable from the other lucky_* siblings (about, tariff lookup, freight quote, etc.).

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 closing sentence explicitly names the intents it serves (「集運怎麼用／流程是什麼／怎麼從淘寶買東西寄回台灣」), giving clear when-to-use context. It stops short of naming alternatives or when-not-to-use (e.g., versus lucky_about or lucky_freight_quote for a pure rate question), so it is strong but not complete routing guidance.

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