outreach_sequence_generate_outreach_sequence

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

No annotations provided, so description carries burden. It describes what the tool generates (touchpoints, content) but does not disclose behavioral traits like output format constraints, rate limits, or side effects.

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 with a semicolon, concise and front-loaded with key info. No fluff, but could benefit from listing parameters briefly.

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?

With 13 parameters and no output schema, the description is insufficient. It does not explain required parameters or provide enough context for an AI agent to correctly invoke the tool.

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 coverage is only 8% (only sequence_length has description). The description adds minimal meaning to the 13 parameters, failing to explain key inputs like company_website, outreach_goal, or seller_product.

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 a multi-channel outreach sequence with 3-8 touchpoints across email and LinkedIn, and lists specific output elements. This distinguishes it from siblings like outreach_drafter_draft_outreach and outreach_strategist_generate_outreach_strategy.

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 explicit guidance on when to use this tool versus alternatives. The description implies it's for generating a full sequence, but does not provide exclusion criteria or compare with siblings.

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