forward_messages

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that drop_author=true removes the 'Forwarded from' header and makes the message appear as a normal message. However, it does not mention permissions, error behavior, or what happens with invalid message IDs.

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 two short sentences with no filler. The main action is front-loaded, and the second sentence adds meaningful detail about the drop_author flag without waste.

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?

The description covers the core action and the key behavioral flag, and an output schema is present. Still, it lacks detail about required parameter semantics, chat identifier format, and edge cases, making it adequate but incomplete for a mutation tool with no annotations.

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 0%, so the description must compensate. It explains only drop_author; from_chat, to_chat, and message_ids remain undocumented beyond their names. In particular, the expected format of chat identifiers is unclear, leaving required parameters underspecified.

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 and resource: 'forward messages from one chat to another.' It clearly conveys the core action and is distinguishable from siblings by its narrow forwarding function, though it does not explicitly name an alternative such as send_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?

The usage is implied by the action itself: use this when existing messages need to be forwarded to another chat. However, there is no explicit guidance about when not to use it or how it compares to alternatives like send_message or edit_message.

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