Чаты

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context: pagination offset is relative to the beginning of the list, next-page offset comes from a prompt in the response header, and archive mode changes the visible set. This goes beyond what the annotations communicate.

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 compact, front-loaded with the purpose, and each sentence earns its place: purpose, parameter semantics, and sibling disambiguation. There is no redundant or boilerplate text.

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 that an output schema exists and the annotations establish safety and idempotence, the description is complete enough for correct use. It covers pagination, archive behavior, the query parameter meanings, and protects against a likely confusion with messenger_messages.

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 0%, but the description fully compensates by explaining both parameters: offset means which chat to start from and carries pagination guidance, archived=True selects archived chats. It also warns about the offset trap with messenger_messages, which is critical for correct invocation.

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 opens with 'Список чатов', a clear verb+resource statement, and adds that it returns one page. It also explicitly distinguishes itself from messenger_messages on the offset semantics, so an agent can tell the two sibling tools apart.

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 gives concrete invocation guidance: how to compute the next page offset, what archived=True means, and explicitly warns not to reuse offset from messenger_messages because the counting direction differs. It makes the intended usage clear even though it doesn't enumerate all when-not-to-use cases.

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