Get Chats Inside Specific Folder

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is fully covered without description help. The description adds only scope information ('all chats and channels'), saying nothing about pagination, ordering, or what an empty/missing folder returns.

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 short sentences, no redundancy, with the core purpose front-loaded and the routing hint second. Every sentence earns its place.

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?

A read-only lookup with an output schema (so return values need not be described), full parameter coverage, and annotations covering safety. The remaining gap is only the absence of pagination/ordering notes, which is minor for this simple tool.

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%: folder_id and account are both documented in the schema (folder_id as the Telegram dialog filter identifier, account for multi-account behavior). The description adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 states a specific verb and resource: retrieving the chats and channels contained in a given dialog folder ID. The title ('Get Chats Inside Specific Folder') usefully corrects the potentially misleading name 'get_folder', which could otherwise be read as fetching folder metadata itself.

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?

It gives a usage cue ('Use when navigating folder contents') and explicitly routes to the alternative for a related need ('To list available folders, use list_folders'). There is no when-not guidance (e.g., single-chat lookup vs get_chat), but the key sibling boundary is drawn.

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