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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds some behavioral context by stating what is returned (order and links) and the required ID provenance, but it does not add richer detail such as error behavior or edge cases. This is adequate given the annotation coverage.

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 focused sentences with no filler. The main behavior and correct ID source are front-loaded, and the exclusion/alternative is stated second, making the description easy to scan and act on.

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?

The tool is simple with one parameter, a full output schema, and annotations that cover the safety profile. The description supplies the essential selection and invocation guidance, including the correct source of the ID and the alternative for a different ID type. Nothing critical is missing.

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 input schema already documents order_id with a clear description, but the tool description adds the important provenance detail 'из list_orders', which is not present in the schema. This helps the agent understand where to obtain the correct value, going beyond the schema's type and constraints.

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 ('Возвращает') and resource ('заказ кабинета и ссылки'), and identifies the exact identifier type (cabinet_order_id from list_orders). It also clearly differentiates from the sibling get_orders_by_woo_id by naming what it is not for.

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 explicitly says the WooCommerce number from email does not belong here and instructs to use get_orders_by_woo_id instead. This gives the agent a direct routing rule and prevents a common misuse.

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