telegram-forward-message

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

The description only states the basic function. It does not disclose behavioral traits such as whether the original message is preserved, if sender info is kept, or permission requirements. Annotations are minimal (readOnlyHint=false, openWorldHint=true) and description does not add context beyond annotations.

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?

Single sentence, no wasted words. Efficiently conveys the core functionality.

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 the complexity of message forwarding (e.g., how forwarding works in Telegram, whether it's a copy or move, limitations), the description is insufficient. No output schema exists to explain return values. The description lacks essential behavioral details.

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%, so the schema already documents the three parameters (fromChatId, toChatId, messageIds). The description adds no additional meaning beyond a general statement of purpose. 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 'Forward messages between Telegram chats' clearly states the action (forward) and the resource (messages between chats), distinguishing it from siblings like send-message or edit-message.

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?

No guidance on when to use this tool versus alternatives like send-message or when not to use it (e.g., limitations on forwarding to specific chat types). No exclusion criteria or context provided.

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