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

Annotations mark the tool as openWorldHint=true and destructiveHint=true, while the description claims it 'uses buyer-supplied information only,' performs 'no external research or outbound actions,' and returns a draft for human review. This is a direct conflict in safety signals: either the annotations overstate side effects or the description understates them. The agent cannot trust the behavioral model.

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 three compact sentences with no filler. Purpose, input constraints, output behavior, and pricing/payment are each addressed in a front-loaded, scannable way.

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?

There is no output schema, zero parameter descriptions, and a contradiction with the annotations, so the definition does not give an agent enough to confidently construct a correct call. The high-level purpose is clear, but payment mechanics, parameter semantics, and side-effect behavior remain ambiguous.

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 by explaining the parameters. It only gestures at 'meeting or conversation notes' and 'buyer-supplied information,' leaving brief, source_text, audience, result_expires, idempotency_key, result_signature, and payment_signature semantically unexplained. It also does not map 'explicit wallet authorization' to the payment_signature field.

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 opens with a specific action ('Draft a follow-up') and specifies the source ('supplied meeting or conversation notes') and content scope ('confirmed actions and dates only'). This clearly distinguishes it from sibling drafting tools such as outreach_email_draft or newsletter_draft.

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: use it for follow-up drafts from buyer-supplied notes, and it explicitly states that no external research or outbound actions are performed. It does not name alternatives or state explicit when-not-to-use conditions, so it stops short of full routing guidance.

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