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

Annotations declare openWorldHint=true and destructiveHint=true, but the description states 'no external research or outbound actions' and 'do not send it.' This is a direct contradiction: the description claims no world-modifying effects while annotations indicate otherwise. Per rubric, a contradiction warrants a score of 1.

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 compact and well-structured: action, constraints, return value, and pricing in four sentences. Every sentence carries unique information with no filler or redundancy.

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 5 parameters, a nested input object, no output schema, and contradictory annotations, the description omits essential parameter meanings and does not clarify how the payment authorization workflow operates beyond 'explicit wallet authorization.' It covers purpose and constraints well but is substantially incomplete for correct invocation.

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%, so the description must compensate for the undocumented parameters. It only refers vaguely to 'supplied business context' and 'buyer-supplied information,' which weakly maps to the nested input but does not explain the difference between brief, source_text, or audience, nor the purpose of result_expires or payment signatures.

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: 'Draft a concise personalized outreach email using supplied business context.' It adds critical constraints ('do not send it or invent personalization') that distinguish it from sending or research tools. This goes well beyond the title and is not a tautology.

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 gives clear usage context: it is for drafting outreach emails from buyer-supplied information, explicitly ruling out sending, external research, and outbound actions. It does not name sibling tools like followup_email_draft or outreach_sequence_draft, but the boundaries are clear enough for an agent to select it.

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