forward_message

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

With no annotations provided, the description must fully describe behavioral traits. It only states 'Forward a message to another chat', which implies creating a copy, but does not disclose whether the original is kept, whether the forwarded message is editable, permissions required, or any side effects. Significant gaps exist for a mutation tool.

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 description is a single concise sentence, front-loaded with the action and target. No filler or redundant information.

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 mutation tool with no annotations and no output schema, the description is thin. It does not explain return values, error cases, or nuances like cross-chat permissions and media support. The simple schema covers parameters, but contextual guidance is missing, making the tool less trustworthy for autonomous agents.

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%, with each parameter (fromChatId, messageId, toChatId) having its own description. The description adds little beyond the schema, but the phrase 'another chat' reinforces the destination semantic. Baseline 3 is appropriate since the schema carries the parameter meaning.

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 uses a specific verb ('forward') and resource ('message'), indicating it forwards an existing message to another chat. It distinguishes from siblings like send_message by implying a re-post of an existing message, but it does not explicitly state that the message must already exist.

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 is provided on when to use this tool versus send_message or other messaging tools. It does not mention prerequisites, such as whether the user must be a member of both chats, or whether the tool is appropriate for media messages.

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