get_1c_documents

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

With no annotations, the description carries the full burden. It discloses a prerequisite ('Требует настроенного подключения к 1С') but does not explicitly state it is a read-only operation or describe response format, error handling, or performance implications. The verb 'Получает' implies retrieval, but lacks explicit safety assurances.

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, front-loaded with the primary action and resource. The examples of document types and the prerequisite are both valuable additions without redundancy.

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 has 6 parameters and no output schema. The description covers purpose, filters, and prerequisites, but lacks any description of the returned document structure or pagination behavior beyond the limit parameter. This is adequate but leaves gaps for an agent needing to interpret results.

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%, so baseline is 3. The tool description adds examples of document types and filter categories, but mostly restates what the schema already covers. The detailed parameter descriptions in the schema handle the semantics.

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 clearly states a specific verb and resource: 'Получает документы из рабочей базы 1С:БИТ.ФИНАНС' with concrete document examples (путевые листы, платёжные поручения). It distinguishes itself from siblings like get_1c_metadata or execute_1c_query by focusing on document retrieval with filtering.

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 usage through its stated filtering capabilities and prerequisite connection, but does not explicitly contrast with alternative tools like execute_1c_query or specify when not to use. It does hint at a workflow by referencing get_1c_metadata in the schema parameter description for document types.

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