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

Beyond the annotations, the description adds useful behavioral context: the created draft is pending review, and actual sending is deferred to the email draft send step and requires 'communications:send'. This clarifies side effects and permission expectations. There is no contradiction with the annotations.

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 brief and front-loaded with the core purpose. Both sentences earn their place, though the phrase 'Sending stays on email draft send' is awkwardly worded. No unnecessary detail is included.

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?

For a tool with 8 parameters, 0% schema description coverage, and no output schema, this description is far from complete. It communicates the high-level workflow but leaves critical invocation details—what each parameter means, what the response contains, and how the pending-review draft is referenced afterward—unexplained.

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 description coverage is 0%, and the description provides no parameter-level meaning. There are 8 parameters including opaque ones like request_id, idempotency_key, outreach_intent_key, and personalization_instruction, none of which are explained. The description completely fails to compensate for the schema's lack of documentation.

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 a specific verb and resource: 'Create a pending review prospect outreach email draft.' The phrase 'pending review' adds meaningful scope and distinguishes this from an actual send operation. It does not explicitly name an alternative sibling, but the behavior is clear enough.

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 when to use this tool: to create a draft for review, not to send it. 'Sending stays on email draft send' provides a useful boundary and points toward the separate send flow. However, it does not explicitly name an alternative tool or state conditions for choosing this over related prospect/email draft tools.

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