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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured fields. The description adds content-scope context (which categories of rules are covered) but says nothing about the form of the answer, e.g. that it returns static reference text rather than a computed quote. A 3 is appropriate given the annotations carry the behavioral burden.

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 sentences, purpose front-loaded, alternative routing second. The Ukrainian term parentheticals (накладна, інвойс) earn their place as query-matching cues rather than filler, though the sentence is somewhat dense.

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 parameters, no output schema and annotations covering safety, the description supplies everything an agent needs to select and call it. The only residual gap is that it does not indicate whether the response is a static policy summary or per-destination rules, which matters given the worldwide scope claim.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless lookup by not suggesting any filters or item identifiers.

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 resource (general shipping rules with SEMERO) and enumerates its scope: required information and documents (invoice, packing list), document vs parcel categories. It also explicitly contrasts with the sibling restricted_items, so an agent can distinguish it from restricted_items without opening either schema.

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?

Gives an explicit trigger (user asks how to prepare a shipment or what documents are needed) and an explicit alternative routing rule ('For a specific item use restricted_items'). Both when-to-use and when-to-use-something-else are present.

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