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

Annotations already declare readOnlyHint/destructiveHint=false, so "Read-only" is redundant, but the description adds real behavioural context: newest-first ordering and the eventual-consistency rule that a chat only appears once the bot has been added. It does not mention pagination or result limits, which is the main remaining gap for a list operation.

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?

Purpose and return shape are front-loaded in the first sentence, followed by compact behavioural notes. It is dense but every sentence carries information; the redundant "Read-only" is the only wasted clause.

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 output schema, the description properly compensates by naming the returned fields and their meaning (numeric chatId for flows, admin/invite/remove rights). Combined with the schema's documented optional filters, an agent has enough to call it; only pagination/volume behaviour is unaddressed.

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%, so botId, kinds and the applicationId/MCP_APPLICATION_REQUIRED failure mode are already fully documented in the schema. The description adds no parameter-level guidance of its own, so the 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 gives a specific verb and resource ("List the groups and channels the application's bots were added to") and even enumerates the returned fields (title, kind, chatId, added time, admin rights), so an agent knows exactly what comes back. It does not name or contrast a sibling tool (e.g. list_watched_groups or list_telegram_operations), so differentiation relies on inference from the resource wording.

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?

"Use this instead of asking the owner for a chat ID" gives a clear positive trigger and rules out a competing behaviour. It also explains an interpretation case ("when the owner's chat is missing, the bot is not in it yet"), but offers no explicit when-not or alternative-tool routing among the many list_* siblings.

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