Заказы

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds that it returns orders with composition and status over a period, and provides date format examples (e.g., 'вчера', '-7d'), which is useful context beyond annotations.

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 concise sentences: the first states the tool's purpose and scope, the second provides concrete date syntax. No wasted words, and the key purpose is front-loaded.

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 read-only query tool with 8 optional parameters and no required fields, the description is complete. It explains what data is returned (orders with composition and status), gives date format guidance, and relies on the schema for parameter details. No output schema is present, but the description does not need to cover return structure beyond what it states.

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 100% with all parameters described, so baseline is 3. The description adds value by specifying acceptable date formats (e.g., '2026-09-06', '06.09.2026', 'вчера', '-7d') which directly clarifies the 'begin' and 'end' parameters, going beyond the schema's generic descriptions.

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?

Description clearly states it returns orders (deals) over a period with composition and status, and enumerates the specific questions it answers ('what was ordered', 'order status', 'how much shipped'). This is specific and distinguishes it from siblings like smartup_order (single order) and smartup_sales (analytics).

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 implies when to use it by listing the queries it answers, but does not explicitly mention alternatives or when not to use it. However, the intent is clear enough for an agent to select it for order-listing questions, so it earns a 4.

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