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

Annotations already flag destructive/ openWorld/ non-idempotent, and the description goes well beyond them: concrete rate caps (5/hour, 15/day), a deliberate pause before each join, the four possible outcomes (joined, already, pending, plus title/username), and the consequence of bulk joining. This is exactly the extra context annotations cannot carry.

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, front-loaded with the action and its accepted inputs before the constraints and the return values. No filler; the parenthetical caps and error codes are load-bearing operational detail.

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, yet the description enumerates the returned fields (joined, already, pending, title, username), documents failure modes, and covers rate limits and the post-join verification step. An agent could invoke this correctly without further information.

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 must compensate and it does: it defines the accepted link syntaxes (public @username / t.me/username, or a t.me/+hash invite), and clarifies that account_id maps to tg_account_id with account_uuid as an alternative identifier. All three parameters gain meaning beyond the bare schema.

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 (join), a specific resource (one Telegram channel/group) and the accepted link forms, so it is immediately distinguishable from list_tg_targets, sync_tg_targets and list_tg_matches. The '[publish]' tag and 'ONE' scope add further precision.

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?

Explicitly says to call it once per group, never in a loop, and to stop on ERR_TG_RATE_LIMITED / ERR_TG_FLOOD_WAIT. It also redirects the agent to list_tg_targets and warns that membership is not the same as posting rights, naming can_post as the field to verify.

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