get_list

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

The description indicates a read-only operation returning a list, which implies no side effects. However, without annotations, it does not explicitly state safety, permissions, or performance characteristics. It mentions pagination and filter, adding some behavioral context but not comprehensive.

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, clear sentence in Russian. It is concise and directly states the function without extraneous information. Could be slightly more structured but effectively communicates the main points.

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 the absence of an output schema, the description explains the return fields (code, name, UUID). It covers pagination and filtering, which are key for list tools. However, it omits error handling, supported object types, or default behavior, which would enhance completeness.

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 provides descriptions for all 4 parameters (100% coverage). The description adds no additional meaning beyond what the schema offers, though it does hint at the return structure. Baseline 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 clearly states it retrieves a list of objects of a specified type with pagination and filtering, and mentions the return fields (code, name, UUID). It effectively conveys the core purpose but does not explicitly distinguish from sibling tools like get_document_list or get_object_attributes.

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?

No guidance on when to use this tool versus alternatives (e.g., get_document_list, get_object_attributes). No exclusions or prerequisites mentioned. The description implies use for listing objects but lacks context on when pagination or filtering is appropriate.

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