forward_message

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

The description discloses the critical behavioral trait: it defaults to dry-run (preview only) and requires dry_run=False to send. No annotations are provided, so the description carries full burden; it adequately covers the main behavioral nuance, though it could mention side effects (e.g., creating a sent copy).

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 sentences long, with no wasted words. It front-loads the core action ('Forward a message') and immediately addresses the key behavioral twist (dry-run default). Every sentence earns its place.

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?

Despite having an output schema, the tool has 6 parameters (2 required) and moderate complexity. The description does not mention required parameters, the recipient list format, or optional body customization. A more complete description would list key parameters or provide a quick example.

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 description explains only the 'dry_run' parameter explicitly. For 6 parameters with 0% schema description coverage, the description fails to add meaning for 'to', 'body', 'send_as', 'account_id', and 'message_id'. Parameter meanings are left to inference from names, which is insufficient.

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 verb 'forward' and the resource 'message', and distinguishes from siblings like 'send_message' and 'reply_to_message' by mentioning the dry-run behavior. It is specific and leaves no ambiguity about what the tool does.

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 description implies usage context: forwarding a message with an optional dry-run preview. It does not explicitly state when not to use or list alternatives, but the name and brief instructions ('Set dry_run=False to actually send') provide sufficient guidance for most agents.

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