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

Annotations already flag a destructive, non-read-only, open-world write, and the description adds substantial context beyond them: the call is only proposed, returns status='confirmation_required' with an action_id and plan_token, and the write happens only after confirm_action. It also discloses the separate result reporting and the conditional connect_url return value.

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 action is front-loaded in the first sentence and each subsequent sentence adds distinct value (scope exclusion, return values, confirmation flow). It is longer than average but almost every clause earns its place; only the double negative phrasing around personal notifications is slightly dense.

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 two-parameter write tool with no output schema, the description covers the confirmation lifecycle, the conditional connect_url, and the scope boundary well. The remaining gap is what the enabled flag means and whether the operation can be reversed or re-run, which matters for a destructive-flagged tool.

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 explains telegram_bot_token ('optionally set the bot token') but says nothing about the enabled boolean — whether false disables alerts, omits the change, or is required to confirm intent — so half the parameters remain semantically ambiguous.

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 (enable Telegram NEW-LEAD alerts) plus the precise scope (caller's active workspace, caller's own Lead Center bot group chat). It explicitly contrasts this with personal reminders via @OrgLinesBot, so the agent can tell what this tool does and does not cover 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?

Gives clear when-to-use context and a firm when-not-to-use boundary (personal reminders/notifications are out of scope and require a one-time link tap). It does not name a sibling tool such as confirm_action as the follow-on in the main body, though it does reference it inside the confirmation paragraph, leaving some routing to inference.

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