hey_forward

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

Description discloses that forwarding is immediate and non-destructive (thread unchanged), and mentions the return shape {success, error?}, adding value beyond annotations. Could include more on authorization or error conditions.

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?

Three concise sentences, each serving a purpose: action/effect, key behavior, and usage guidance. No extraneous 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?

Covers purpose, usage, and return type for a simple forwarding tool. Lacks details on error handling or behavior with invalid entry_id, but adequate given tool complexity.

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?

With 100% schema coverage, the description adds little beyond the schema. It reinforces that body is optional but does not provide additional semantic or formatting guidance.

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 an existing email immediately and notes the original thread remains unchanged, distinguishing it from siblings like hey_send_email and hey_reply.

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?

Explicitly instructs to use this tool instead of hey_send_email for sharing existing content and hey_reply for replying within a thread, providing clear when-to-use and alternatives.

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