list_folders

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the key behavioral fact that this returns ALL folders with no filtering or parameters, which contextualizes why it's parameterless. Slight gap: no mention of ordering or whether archived folders are included.

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?

Single front-loaded sentence with no waste; every word earns its place. Ideal for a simple parameterless list tool.

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?

For a trivial zero-param read tool with annotations covering the safety profile, the description is nearly sufficient. However, it does not clarify return shape (e.g., array of folder names) or whether it includes default/all chats folder, leaving a minor gap.

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?

Tool takes zero parameters, so the baseline is 4. The description correctly communicates the no-argument nature and implies a complete listing, which matches the empty schema. No additional parameter detail is possible or needed.

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?

States a specific verb 'List' and resource 'Telegram chat folders'. Distinguished from siblings like list_chats (lists chats, not folders) and get_messages (retrieves messages). No ambiguity for an agent.

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 explicit when-to-use or when-not-to-use guidance, though the scope ('folders') implies it's the tool for enumerating chat folders. Sibling tool list_chats makes the distinction clear enough, but the description does not state it.

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