create-draft-email

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

Annotations indicate destructiveHint=true, but creating a draft is not destructive. The description contradicts both the annotations and the tool's actual behavior (creating a draft vs. open extensions). There is no clarity on side effects or prerequisites.

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 short but contains irrelevant content about open extensions. It is concise but incorrect, providing no useful information for the actual tool purpose.

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 complexity of the input schema with nested objects, the description is completely inadequate. It fails to explain what the tool does, what the required parameters are, or how to use it. It does not mention creation of a draft email at all.

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 has many parameters like subject, body, toRecipients, etc., but the description does not explain their use in the context of creating a draft email. Schema description coverage is 67%, but the description fails to add meaning 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 describes creating an open extension and adding custom properties, which is unrelated to the tool name 'create-draft-email'. The input schema clearly includes email fields like subject, toRecipients, body, indicating this tool creates a draft email, but the description is entirely mismatched and misleading.

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 provides no guidance on when to use this tool versus alternatives like create-reply-draft or create-forward-draft. It does not state when to use it to create a draft email, and instead describes a different operation (open extensions).

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