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

No annotations exist, so the description carries the full disclosure burden, and it discloses nothing: no auth requirements, no pagination or ordering behavior, no indication of whether this is a read-only enumeration or what volume of results to expect. A single phrase cannot cover behavior for an unannotated tool.

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?

It is short, but this is under-specification rather than conciseness: one colon-separated fragment that spends its words repeating the tool name instead of front-loading useful scope information.

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?

With no annotations and no output schema, the description must explain what a dialog record contains and how results are shaped; it does none of that. For an agent deciding between this and resolve_user/converse, the definition is insufficient.

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% and the single optional limit parameter is documented in the schema as "Max dialogs to return (default 100)". The description adds nothing beyond that, so the baseline of 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 is essentially the tool name plus a platform prefix: "Telegram: list dialogs" restates list_dialogs with no added scope, target, or content detail. It does signal the platform, but a reader gains nothing about what a dialog is or which ones are returned.

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 call this versus siblings like converse, resolve_user, or list_active_chat_participants. The agent must infer that this is a discovery/enumeration entry point before messaging.

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