outreach_drafter_render_outreach_html

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

The description reveals the tool transforms an outreach package into HTML, but does not explicitly state it is a pure render without side effects. No annotations are provided, so the description must carry this burden; it provides moderate context but lacks details on permissions, rate limits, or data handling.

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 a single sentence, which is concise. It front-loads the main purpose. However, it lacks any structural elements like bullet points or separate sections that could improve readability.

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?

Given the absence of annotations and output schema, the description should provide more context about the output format, prerequisites, or potential side effects. It only mentions the content of the HTML but not how to use the output or what the output variable represents.

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%, requiring the description to compensate for parameter meanings. However, the description does not elaborate on the two parameters (outreach_package, output_variable_name) at all, leaving the agent to infer their purpose from names alone.

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 the tool's function: rendering an outreach package into professional HTML. It mentions specific outputs (email variants, LinkedIn messages, personalization audit) which distinguishes it from sibling tools like outreach_drafter_draft_outreach or outreach_sequence_generate_outreach_sequence.

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 alternatives. It does not specify prerequisites (like needing to draft an outreach package first) or contexts in which this tool is appropriate. No exclusions or alternatives mentioned.

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