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

Annotations already declare it non-read-only, non-idempotent, open-world and non-destructive. The description adds meaningful operational context beyond that: customer liability for supplying valid codes/data, and the explicit non-scope (no issuing/legalizing/validating). It omits any note on downstream effects or timing, so not a 5.

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 tight, front-loaded sentences: the action and scope come first, the liability/limitation clause second. Little wasted text, though the missing parameter explanation means the brevity is partly under-specification.

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?

An output schema exists, so return values need not be described. But for a 6-parameter request-submission tool with 0% schema coverage, the description leaves parameters wholly unexplained, which an agent needs in order to invoke it correctly.

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% across 6 parameters and the description explains none of them (task, contact, subject, language, location, confirm_submission). 'Optional photo evidence' is mentioned but no photo parameter exists in the schema, so it does not compensate for the coverage gap.

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 states a specific verb-resource pair: requests organizing the application of customer-provided Chestny ZNAK marking codes/labels to goods in China before shipment. This is clearly scoped and cannot be confused with the sourcing/verification siblings, though it names no sibling explicitly.

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?

It gives context ('before shipment') and useful boundaries ('does not issue, legalize or validate marking codes'), which imply when to use it. However, it never states when NOT to use it in favor of an alternative, nor names a sibling tool, so usage is only implied.

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