draft_pr_outreach_for_contacts

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

No annotations are provided, so the description carries full burden. It discloses that the tool drafts emails (non-destructive) and includes public demo status, but does not detail side effects, auth requirements, rate limits, or storage behavior.

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 provide a complete overview without fluff. The first sentence defines the core function, and the second enumerates draft components, making it easy to parse.

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?

Description covers the tool's output but lacks details on return format (no output schema), integration with sibling tools (e.g., when to use after 'build_contact_list'), and the meaning of 'Public demo' for usage constraints. Adequate but not comprehensive.

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 low (33%) with only the 'contacts' parameter having a meaningful description. The description fails to explain the 'sender' object structure or 'tone' enum options, leaving agents to infer from context. It adds minimal value beyond the schema.

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?

Description clearly states the tool drafts personalized PR outreach emails per contact, grouped by source. It lists specific components (hook, pitch, reason, meeting ask, CTA), distinguishing it from sibling tools like 'draft_outreach_for_event' which targets events.

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 after building a contact list (mentioning 'From build_contact_list or user-supplied' in input schema), but does not explicitly state when to use this tool vs alternatives like 'draft_outreach_for_event' or 'queue_pr_outreach_job'. No exclusions or prerequisites are mentioned.

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