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

Annotations already establish that this is a non-read-only, non-idempotent, non-destructive write. The description adds real context beyond that: member resolution by username/phone/JID and the fact that an already-present member is reported rather than erroring, which is behaviorally important for a non-idempotent tool. It stops short of noting required permissions or failure modes.

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 one-line purpose, then a short bulleted breakdown and a returns line. The 'What this does:' header is mild padding, but each bullet carries distinct information and nothing is repeated.

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?

With no output schema, the explicit 'Returns: success, chat_id, member, already_member' line is valuable and fills that gap. For a four-parameter mutation tool with full annotation coverage, the description covers purpose, resolution, and return shape; only permission requirements and error behavior are left unstated.

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 100%, and the schema itself carries the detailed chat_id format rules ('never compose one', signed numeric id vs @g.us JID) plus per-channel member formats. The description's 'resolves the member by username, phone number, or JID' only lightly restates that, so the baseline of 3 is appropriate.

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 opens with a precise verb+resource+scope: 'Add a member to an existing group on Telegram or WhatsApp.' The 'existing group' qualifier separates it from group_create, and 'add a member' separates it from group_join. It never names those siblings explicitly, so an agent must infer the boundary, but the purpose itself is unambiguous.

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?

Usage is only implied: the tool applies when a group already exists and you know a username/phone/JID. There is no statement of when to prefer this over group_join, group_add, or group_promote_admin, and no mention of prerequisites such as needing admin rights. Adequate but with a clear routing gap.

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