outreach_strategist_generate_outreach_strategy

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

No annotations are provided, so the description carries full burden. It mentions that providing a LinkedIn URL enriches output with warm-up suggestions, which is useful. However, it does not disclose whether the tool is read-only, requires authentication, has rate limits, or modifies any data. The behavioral disclosure is partial.

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 primary action and output. Every word adds value, no 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 a tool with 11 parameters, no output schema, and many siblings, the description adequately explains the output components and positions the tool. It could be more complete by specifying the output structure (e.g., text, JSON), but it is sufficient for an agent to understand the tool's role.

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 high (91%), so the baseline is 3. The description adds marginal value by noting the LinkedIn URL enriches output, but otherwise does not elaborate on parameter meanings 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 clearly states that the tool analyzes a prospect's context and produces a structured Outreach Strategy Brief, listing specific components (messaging angle, channel priority, CTA approach, timing assessment, risk factors). It also positions itself as the 'entry point to the Sales Outreach Team workflow', distinguishing it from sibling tools like outreach_drafter_draft_outreach.

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 as the first step in the outreach workflow, but does not explicitly state when to use it versus alternatives, nor does it provide exclusions or prerequisites. The guidance is clear but not comprehensive.

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