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

Annotations already declare readOnlyHint and non-destructive, so safety is covered; the description adds real behavioral substance beyond that — unlisted groups are dropped, their contacts never materialize, and DMs bypass the filter. It stops short of describing the returned shape or ordering, which is a minor gap for a list tool with no output schema.

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?

Four tight sentences with no filler; the core purpose and read-only constraint come first and the fail-closed semantics follow. Slightly dense but every sentence carries 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?

For a zero-required-param read tool, the description covers purpose, safety posture, filtering semantics, and the botId default — enough to call it correctly. The missing piece is the relationship to list_bot_chats and set_watched_groups, which would complete the picture.

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 coverage is 100%, so both parameters are fully documented in the schema. The description only echoes the botId omission rule already present in the schema and says nothing about applicationId defaulting, 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?

States a specific verb and resource ('List the group/channel chats a telegram_mtproto userbot monitors'), which is far more precise than the bare name. It does not, however, distinguish itself from the sibling list_bot_chats, so an agent still has to infer which listing is which.

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 gives strong 'what this means' context (fail-closed filtering, DMs always pass) but never states when to call this versus list_bot_chats or the paired set_watched_groups. Usage is implied by the source-of-truth framing rather than explicitly routed.

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