create-forward-draft

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

The description clarifies that the tool creates a draft and does not send, which is a critical behavioral detail beyond the annotations. The annotations indicate destructiveHint: true, which may imply modification, but creating a draft is not inherently destructive. No contradiction is present.

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 very concise: two sentences and a tip. Every part adds value, and the key information ('does not send') is front-loaded.

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 the tool's simplicity and the presence of annotations, the description is mostly complete. It lacks details on return behavior or specific parameter usage, but the tip compensates for basic usage context.

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 does not discuss parameters; however, schema coverage is high (75%), so the schema provides adequate meaning for most parameters. The description adds no additional parameter context.

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 explicitly states 'Create a forward draft (does not send)', clarifying both the action (create forward) and a key behavioral trait (not sending). This distinguishes it from siblings like forward-mail-message (which sends) and send-draft-message.

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 includes a tip: 'Useful when user wants to review before sending', which guides when to use the tool. However, it does not explicitly mention when not to use it or list alternatives.

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