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

The annotations already flag destructiveHint=true and openWorldHint=true, but the description adds useful behavioral context: each day it finds fits scoring 8/10 or better, writes to decision-makers, sends real email within the daily limit, and sent email cannot be recalled. This meaningfully explains the real-world consequence beyond the annotations, though it does not cover update-vs-create behavior or failure modes.

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 two sentences, front-loaded with the core action and followed by the most important behavioral consequence. Every sentence adds useful information without repetition or filler.

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 an 8-parameter destructive mutation tool with no output schema, the description gives a strong operational picture: ongoing daily outreach, fit scoring, real email sending, daily limits, and irreversibility. It leaves some gaps around create-vs-update semantics and prerequisites, but the annotations and schema carry the remaining structural details.

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 75%, so the schema already documents most parameters, including productDomain, senderEmail, targeting, angle, dailyLimit, and leadSource. The description reinforces the single-product scope and daily limit but adds little parameter-level meaning beyond what the schema provides.

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 uses a specific verb and resource: 'Create or change the autopilot for one product and turn it on or off.' It clearly scopes the tool to a single product and distinguishes enabling/disabling, but it does not explicitly name sibling tools such as draft_outreach_emails or send_reply to clarify boundaries.

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 usage: this is for setting up or modifying persistent automated outreach that runs daily. However, it does not state when to choose this over draft_outreach_emails, send_reply, or list_autopilots, nor does it give exclusions or prerequisites beyond the daily send limit.

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