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

Discloses the 300-second poll cadence, the notice payload fields, that notices never contain text, that repeats can occur and should be ignored by event_id, and that the watch is session-scoped. The only gap is that with destructiveHint=true the description never says what persistent state is created or whether setup can disturb existing watches; it implies but does not state that.

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?

Front-loads purpose in the first clause and packs lifecycle, payload, and client-certification caveats efficiently. It is a dense run-on paragraph, but virtually every sentence carries information an agent needs.

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?

Covers the full arc an agent needs for a subscription-style tool: setup requirements, latency expectation, payload shape, deduplication, catch-up advice, and termination. Output schema handles return detail, so nothing material is missing.

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 the schema already explains chats, account, and include_groups. The description only restates that account and chats are needed and points chats to telegram_list_chats, adding little beyond the schema; include_groups is never mentioned in the description.

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: it asks LMCP to notify this session when new messages arrive in chosen Telegram chats. It explicitly contrasts with telegram_read_messages, so an agent can immediately distinguish the push model from the polling sibling.

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?

Gives the exact motivation (avoid repeated polling), names the read alternative for actually fetching text, and names telegram_unwatch_chats as the termination path. It also advises reading chats once to catch up, which is a real usage instruction.

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