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

Annotations already disclose destructive, open-world, non-idempotent write behavior. The description adds concrete behavioral context: live Telegram connection, present=false flagging rather than deletion, refreshed member counts and posting rights, and a rate/loop warning. It does not detail authentication or failure handling, but it meaningfully supplements the annotations.

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?

The description is front-loaded with '[write]' and the core sync behavior, followed by concrete effects, parameter aliasing, return summary, and invocation caution. Every sentence adds value without repetition.

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 mutation sync tool with two parameters, no output schema, and no required fields, the description is largely complete: it covers side effects, return counts, account identifier handling, and loop avoidance. It could say more about prerequisites (connected account) and how it relates to list_tg_targets, but the essential invocation context is present.

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 0%, so the description must compensate. It does so by explaining that account_id corresponds to tg_account_id and that account_uuid is an alternative identifier; this gives enough meaning to invoke either parameter correctly, though no format details are provided.

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 (re-read TG channels/groups) and explains the resulting updates: new targets appear, left targets are flagged present=false, and metadata is refreshed. It is clear what the tool does, though it does not explicitly name sibling tools like list_tg_targets or join_tg_target.

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?

It provides a useful invocation guideline (call once per account, not in a loop) and explains the account_id/account_uuid aliasing. However, it does not explicitly say when to choose this tool versus list_tg_targets or join_tg_target, leaving alternative selection implied.

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