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

Annotations only say readOnly/idempotent/non-destructive/openWorld=false; the description adds real behavioral meaning: STATUS semantics (PASSIVE targets are excluded from publishing) and the 'present' flag (still on the account). It also discloses that the default filter narrows results, which is exactly the kind of hidden filtering behavior an agent must know about.

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-loaded with the resource and its fields, then filters, then the follow-up action; nearly every clause carries information. Slightly dense as one run-on paragraph with an awkward mid-sentence line break, but there is no filler.

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?

No output schema exists, but the description effectively supplies one by enumerating tg_target_id, tg_target_uuid, type, title, username, members count, can_post, is_admin, status and present. Combined with the filter semantics and sync prerequisite, an agent has everything needed to call and interpret it.

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 0%, so the description has to carry all five parameters. It handles account_id well ('account_id = tg_account_id (or pass account_uuid)') and explains only_postable thoroughly, but page and per_page are never mentioned, leaving pagination undocumented in either place.

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?

Opens with an explicit verb+resource+scope: '[read] The channels and groups a Telegram account is in', then enumerates the returned fields. An agent can distinguish this from nearby siblings (list_tg_matches, list_tg_watches, sync_tg_targets, join_tg_target) without opening the schema.

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?

States the default filter behavior ('only_postable (default) keeps the ACTIVE targets the account may post to'), names the downstream consumer (tg_post_target_ids of create_social_post platform tg), and gives an explicit prerequisite fallback ('Call sync_tg_targets first when the list is empty or old'). That is when-to-use plus the alternative route.

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