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

Annotations already flag destructive/openWorld/non-idempotent, and the description adds real operational context beyond them: messages reach the real contact, Telegram accounts can only reply to inbound contacts, per-account rate limiting with the ERR_TG_RATE_LIMITED code and a retry_after that must not be beaten, and ERR_TG_CHAT_OPTOUT for /stop chats.

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 verb and the chat_id lookup path, then layered detail on Telegram and Meta constraints. Some sentences are telegraphically dense (error-code parentheticals, prefixed-key examples), but nothing is padding.

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?

Given five params, no output schema, and a real-world side-effecting send, it covers identifiers, platform enum, extra body injection, opt-out and rate-limit failure modes. The one gap is the return value — no indication of what a successful send yields (message id, status) for the agent to act on.

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 carries the burden and mostly does: platform is enumerated (ig|fb|tw|wp|tg), chat_id and chat_uuid are tied to their source in list_chats, and extra is explained with its prefixed-key convention and examples. Only the message parameter itself is left as self-evident with no length/format guidance.

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 a bracketed verb tag and a specific verb+resource: "[publish] Send a text message into an existing conversation." That phrasing plus the platform enumeration immediately separates it from send_sms, send_email, send_wp_template and start_tg_chat.

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 explicit routing rules: chat_id comes from list_chats, and for a new Telegram contact the agent is pointed to start_tg_chat instead. It also gives exclusion conditions — outside the 24h window ig/fb are limited to one private reply and wp must use send_wp_template.

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