prom_seller_list_orders

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

With no annotations, the description carries the full behavioral burden but delivers only a one-line purpose. It never discloses pagination semantics (despite limit and last_id params), result ordering/default sort behavior, rate limits, or what 'authenticated seller company' implies for permissions.

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 filler, which is appropriately terse. However, the brevity crosses into under-specification for a tool with eight parameters and no supporting annotations.

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 an eight-parameter list tool with no annotations, no output schema, and no description of pagination or filter behavior, the one-sentence description leaves key calling details (how to page, what filters combine, what is returned) undocumented.

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 coverage is 75%, but the description adds zero parameter meaning. Two parameters (status and sort_dir) lack schema descriptions entirely, and the description does not compensate for those gaps or clarify filter/sort/pagination interactions among the eight parameters.

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 ('List orders') with a clear scope ('from the authenticated Prom.ua seller company'), which cleanly separates it from the singular prom_seller_get_order. It does not explicitly name sibling alternatives, but the read/list intent is unambiguous.

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 description offers no guidance on when to use this list tool versus prom_seller_get_order for a single order, nor any conditions or exclusions. An agent must infer usage entirely from the tool name and schema.

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