Forward message

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description adds important behavioral details: the original travels as a quoted snapshot, the optional note is posted as a separate message because Discord does not allow text on the forward itself, and that it functions across channels. This provides a thorough understanding of the tool's behavior.

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 three sentences long, front-loaded with the core action, and every sentence adds meaningful detail without redundancy. It is concise yet comprehensive.

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 tool with 5 parameters and no output schema, the description covers the essential behavior, including the quoted snapshot and note posting. It does not mention permissions or edge cases, but given the simplicity of the operation and good annotations, it is adequately complete.

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?

The input schema already has 100% coverage with descriptions for all parameters. The description adds further meaning by explaining that the 'content' parameter is an optional note posted separately and that the forward includes a quoted snapshot, clarifying how 'message_id' and 'from_channel' relate. This goes beyond the 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 clearly states the tool forwards a message from one channel to another, explicitly referencing the Discord client's forward behavior and the quoted snapshot mechanism. This distinguishes it from sibling tools like send_message or crosspost_message by specifying the exact semantic.

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?

It provides clear context for when to use the tool ('forward a message... the way the Discord client's forward does') and notes that it works across channels in the server. It does not explicitly mention alternatives or when not to use it, but the scenario is well-defined.

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