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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so safety is covered. The description adds a genuinely non-obvious behavioral fact: Lodestone auto-appends a 'Sent via Lodestone' footer on the Free plan, so the agent knows not to duplicate it and that the delivered text differs from what it passes.

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?

Two sentences, zero filler, and the delivery-scope constraint is front-loaded ahead of the plan-specific footer caveat.

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, and the description does not say what the call returns (e.g. a message id) or confirm delivery behavior. For a simple two-parameter send tool with rich schema text and safety annotations, everything else an agent needs 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 coverage is 100%, with both parameters documented, including where to obtain chat_id. The description adds only that chat_id may be a user DM or a group/channel, which is marginal beyond the schema's '@username or numeric id' text. Baseline 3 applies.

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 ('Send a text message through your Telegram bot') plus precise audience scope (a user who has DM'd the bot, or a group/channel the bot is in). An agent can distinguish this from beeper_send_message or email_send without opening any 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?

The parenthetical clarifies the only chats that are reachable, which is real usage guidance for a bot-scoped tool. It stops short of stating exclusions or naming alternatives (e.g. beeper_send_message, or verifying the chat via telegram_get_chat first).

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