Forward messages

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

The only annotation is openWorldHint: true, which is vague. The description does not disclose whether forwarding copies messages (leaving originals intact), any authentication requirements, rate limits, or side effects on the source/destination dialogs. This lack of behavioral detail goes beyond what annotations convey.

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, front-loaded sentence with no unnecessary words. It conveys the core purpose efficiently.

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?

There is no output schema, so the description should explain what the tool returns, but it does not. It also omits the 100-message limit for messageIds and other contextual details such as whether forwarding is available across different dialog types. The description is too sparse for a tool with six parameters.

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 only 17% (only dropAuthor has a description), so the description must compensate. It clarifies that fromPeer and toPeer refer to dialogs and that messageIds are the messages being forwarded, but it leaves silent, accountId, and the exact meaning of messageIds implicit. This is partial compensation but not thorough.

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 clearly states the tool's function with a specific verb and resource: 'Forward messages from one dialog to another.' This distinguishes it from siblings like send_message or edit_message, which serve different purposes.

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?

There is no guidance on when to use this tool versus alternatives such as send_message, nor are any prerequisites or exclusions mentioned. The description simply states what it does, leaving the agent to infer when it should be selected over similar tools.

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