camelot_email_campaign_writer

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds 'Local browser processing' and a canonical URL, which provide some context about where execution happens. However, it doesn't disclose what the output structure looks like or whether the tool persists anything, though the output schema exists to cover return values.

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?

Two sentences with no filler. The core function is front-loaded, and the canonical URL is a minor addition. The trailing double period is a small formatting blemish but doesn't hurt comprehension.

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 content-generation tool with an output schema and full parameter documentation, the description is adequate. The main gap is the lack of explicit differentiation from adjacent email/ad tools, but the output schema and annotations cover most operational concerns.

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 100%, so the schema already documents all three parameters. The description adds no parameter-level detail beyond what the schema provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a specific verb ('Draft') and resource ('structured email marketing sequences with subject lines and body copy'), which clearly distinguishes it from siblings like camelot_cold_outreach_emailer and camelot_ad_copy_template_builder. It could be slightly sharper about the 'campaign' vs 'single email' distinction, but the core purpose is clear.

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 for email marketing campaigns but does not explicitly state when to use this tool versus alternatives like camelot_cold_outreach_emailer or camelot_ad_copy_template_builder. The sibling list contains several adjacent tools, so explicit routing guidance would help, but the context is reasonably clear from the name and description.

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