forward_messages

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows it is a mutating but non-destructive operation. The description adds one useful behavioral detail (album grouping preservation) but says nothing about limits, return values, or error semantics. This adds some value beyond annotations but is not rich.

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 that conveys the core action and a key behavioral nuance. Every word earns its place, with no repetition of schema or annotation 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?

With 6 parameters (3 required), only 17% schema coverage, and no output schema, the description is too minimal to fully orient the agent. It covers purpose and one behavioral trait, but omits parameter roles, return format, and any operational constraints, leaving significant gaps for a mutation tool.

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 only 17%, with chat_id being the only parameter described. The description does not explain the meaning of from_chat_id, message_ids, message_thread_id, disable_notification, or protect_content. It only implies 'messages' are forwarded, but fails to compensate for the sparse schema.

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'), names the resource ('messages'), and includes a scoping qualifier ('multiple at once'). The parenthetical '(maintains album grouping)' distinguishes it from the sibling forward_message and copy_messages tools.

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 phrase 'multiple messages at once' clearly implies use for batch forwarding, and 'maintains album grouping' sets expectations about behavior when forwarding albums. However, it does not explicitly state when to prefer forward_message or copy_messages, so it stops short of full exclusion/alternative guidance.

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