outreach_drafter_draft_outreach

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

With no annotations, the description must disclose behavioral traits. It mentions personalization and an audit but doesn't explain whether the tool saves data, if it's idempotent, or what the audit reveals. Lacks depth for a generative tool.

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?

One sentence is concise but overly terse given the tool's complexity. It front-loads the purpose but omits necessary details, making it adequately structured but insufficiently informative.

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 12 parameters, 4 required, and no output schema or parameter descriptions, this single-sentence description is far from complete. It fails to explain the role of most parameters, the nature of the audit, or the output format.

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 details. The 12 parameters including prospect_name, channel, tone, etc. are not explained. The description adds no semantic value beyond parameter names.

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 it generates personalized email and LinkedIn message variants and mentions a transparent personalization audit. It distinguishes from sibling tools by focusing on drafting variants with an audit feature, though it doesn't explicitly compare with alternatives.

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?

No guidance on when to use this tool versus other outreach tools like outreach_sequence_generate_outreach_sequence or outreach_strategist_generate_outreach_strategy. No prerequisites or exclusions mentioned.

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