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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and the description adds useful context by enumerating the returned fields, including the 'problem' field explaining why a rule may not fire. It doesn't disclose anything beyond the field list, such as ordering or whether the result is exhaustive, but for a zero-parameter list tool that is a minor gap. No contradiction with 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?

One dense sentence that front-loads the subject ('Шаги правил продаж') and packs the entire field inventory into a compact colon-separated list. The heavy parenthetical nesting for action types is slightly dense but contains no filler.

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 simple zero-parameter read-only list tool, the description covers what an agent needs: the structure and meaning of each returned field, with annotations covering safety and idempotency. Since no output schema exists, the field enumeration in the description partially compensates. It could explicitly state that the result is the full set of rules, but this is a minor omission at this complexity level.

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 has no parameters, so the rubric baseline is 4 and there is nothing for the description to add about parameters. The description instead documents the returned item structure, which is the most relevant semantic content for a list tool.

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 name list_sales_rules supplies the verb+resource, and the description explains what a sales rule consists of: trigger (tag or stage with number), delay in minutes, action (bot funnel, tag_add, tag_remove, stage, task, goal), enabled flag, and problem. This distinguishes it from mutation siblings like create_sales_rule and update_sales_rule. However, the description never explicitly states that the tool returns the list of all sales rules.

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?

Usage is implied: this is a read-only listing tool whose output is the configured sales rules with their steps. No explicit when-to-use guidance or alternatives are mentioned, which matters less here because the sibling set contains clear mutations (create/update_sales_rule) rather than competing list tools.

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