execute_query

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

States it is a read tool ('чтения данных'), but no annotations are provided. Lacks details on side effects, performance impact, authentication needs, or error handling. The description carries full burden but only partially addresses it.

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 in Russian, front-loaded with purpose and key capabilities. No unnecessary words; highly efficient.

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?

Given no output schema, the description should indicate result format (e.g., list of records, columns). It lacks this, as well as any mention of pagination behavior, error handling, or usage constraints. Incomplete for effective agent use.

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 basic descriptions. Description adds context that query supports SELECT, joins, groupings, and virtual table parameters, going beyond schema. max_results is not elaborated further.

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 executes arbitrary 1C query language queries for reading data, distinguishing it from more specific sibling tools. Could be more explicit that it is read-only and what domains it covers.

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?

Implied usage as the most powerful read tool, but no explicit guidance on when to use vs alternatives (e.g., simpler get_list tools) or when not to use (e.g., for modifications).

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