wb_dbs_order_meta_get

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

No annotations are provided, so the description carries the full burden of explaining behavior. It does not say whether this tool retrieves metadata, whether it is read-only, what it returns, or how it differs from the related order-meta tools. The description adds almost no behavioral information beyond the name.

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?

The description is short but this is under-specification rather than effective conciseness. It repeats the same idea twice ('order meta' and 'метаданные DBS'), and the single phrase does not earn its place because it conveys no actionable guidance.

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?

For a one-parameter getter with no annotations and no output schema, the description is still far too incomplete. An agent cannot tell what metadata is returned, how order_id should be supplied, whether this applies to DBS-only orders, or how it relates to the very similar wb_order_meta_get and wb_cc_order_meta_get tools.

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%, and the description provides no explanation of order_id or how it is used. The schema only indicates order_id is a required integer, but the description does not clarify whether it is a DBS order ID, a WB order ID, or something else. No value is added beyond the schema.

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 is essentially a restatement of the tool name: 'DBS order meta (метаданные DBS)' labels the resource but does not state what the tool does with it. There is no verb such as 'get' or 'retrieve' in the description, and it does not meaningfully distinguish itself from wb_order_meta_get or wb_cc_order_meta_get beyond the DBS prefix.

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?

No guidance is provided about when to use this tool versus alternatives. Sibling tools like wb_dbs_order_meta_set, wb_dbs_order_meta_delete, wb_order_meta_get, and wb_cc_order_meta_get exist, but the description does not mention any of them or explain the DBS-specific context.

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