list_chats

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

No annotations are provided, so the description carries the full burden. It discloses side effects (fetches new Telegram updates, saves chats to disk), caching behavior (subsequent calls return cached list plus new), and return structure (chats list with fields, hint key). This is strong behavioral disclosure, though it slightly understates the network I/O implication and doesn't mention rate limits.

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?

Well-structured with headers (Persistent discovery, Static config) and a clear returns section. The content is dense but organized. Could arguably drop the 'hint' formatting line ('"Name=chat_id..."') to tighten, but the format example adds genuine value. Slightly verbose but every section 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?

For a zero-parameter tool with an output schema, the description is remarkably complete. It documents both data sources, the caching/refresh behavior, the return structure with field names and types, the 'hint' semantics, and follow-up instructions. Given the tool's complexity (multi-source list with side effects), this is thorough and self-sufficient.

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 tool has zero parameters, so there is nothing for the schema to document. The description compensates by fully explaining the return dict structure (chats with fields, hint), which effectively serves as the parameter/output documentation. Baseline 4 is appropriate for a zero-param tool with a well-documented output.

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?

Description states a specific verb+resource ('List all known chats the bot can send messages to') and clearly distinguishes from siblings. It clarifies it returns chats usable with send_message and other tools, differentiating from get_chat/get_chat_member_count which operate on a specific chat. The scope ('known chats') is well defined.

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 explains when to use this tool (to discover what chats the bot can message) and provides clear context for the two data sources (cached discovery + static config). It also gives guidance on what to do when a desired chat is missing (communicate hint, call again). However, it doesn't explicitly name alternative tools to use instead, though the sibling context makes this somewhat implicit.

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