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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds no behavioral context beyond the topic list: it does not explain that the tool returns reference text, how topic selection behaves, or any other trait beyond what annotations and schema already provide.

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 a single dense comma-separated list with no lead-in statement. It is not verbose, but the lack of structure and front-loaded purpose statement makes it less effective than it could be.

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: one required enum parameter, full schema coverage, and annotations that carry the safety profile. The description lists all covered topics, which is adequate for topic selection, but it omits an explicit statement of what the tool returns and how to use it relative to sibling tools, leaving a gap for an agent deciding among alternatives.

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 100%, and the single enum parameter tema is fully documented in the schema. The description repeats the topic names but adds no mapping, syntax, or meaning beyond what the enum already provides, so the baseline score of 3 is appropriate.

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 enumerates the topics the tool covers (delivery, measurement, installation, warranty, payment, ordering, etc.), which implies it is an information-retrieval tool for store conditions. However, it never states an explicit verb or says that it returns store policy/reference information for the selected topic, and it does not distinguish itself from siblings like poisk, razdely, or tovar.

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?

There is no explicit guidance on when to use this tool versus alternatives. The topic list suggests it is for store-condition questions, but the description does not name any sibling tool, exclusions, or selection conditions.

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