sfc_get_fee

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read, but nothing is said about what the fee represents (per-order fee, shipping charge, surcharge), whether it requires an existing order, or what happens for an invalid/unknown order code.

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 padding. It is terse rather than padded, though the parenthetical method name is the only element beyond the bare minimum.

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 no output schema and no annotations, the description should explain what the returned fee looks like (amount, currency, breakdown) and error behavior. None of that is present, leaving the agent guessing about the response shape for a lookup tool.

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 0%, so the description must compensate. It does add one meaningful bit: the orderCode is the 'SFC order code', distinguishing it from internal identifiers. But no format, example, or validation hints are given for the single required parameter.

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 and resource ('Get fee') plus the key it is looked up by ('SFC order code'), and even names the underlying method (getFeeByOrderCode). It does not distinguish itself from the nearby sibling sfc_get_rates, so an agent may hesitate between the two.

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?

There is no guidance on when to use this versus sfc_get_rates or sfc_preview_order, both of which plausibly return cost information. No prerequisites, no exclusions, no context about which order states this is valid for.

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