create-forward-draft

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

Description adds beyond annotations by stating it creates a draft and does not send. Annotations already indicate destructiveHint=true, so no contradiction. Lacks details on side effects or required permissions.

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?

Very brief, but first sentence 'Invoke action createForward' is nearly a tautology. Tip is useful. Could be more structured but not overly verbose.

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?

Given complex input schema with nested objects, the description is too minimal. No mention of required parameters or output. For a tool with many siblings, it lacks completeness.

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 coverage is 75%, and the description does not add any meaning to parameters. It is adequate given baseline, but does not help agents understand the complex nested body structure.

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?

Description clearly states the tool creates a forward draft and that it does not send. However, it does not differentiate from sibling tools like create-reply-draft or create-draft-email.

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?

Only a tip 'Useful when user wants to review before sending' provides minimal usage context. No explicit when-not or comparison to alternatives like forward-mail-message or send-draft-message.

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