queue_pr_outreach_job

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

With no annotations provided, the description provides useful behavioral context: requires API key, uses verified sender, respects weekly caps, honors suppression list, routes replies. This goes beyond the schema but does not cover all traits like idempotency or error 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 three sentences, front-loaded with purpose and return values, followed by a prerequisite and behavioral details. Every sentence is necessary and adds value.

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 6 parameters, nested objects, and no output schema, the description is insufficient. It lacks explanations for most parameters, fails to describe the dashboard URL or how to use returned job_id, and does not mention output format.

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 17% (only 'groups' has a description). The description does not add meaning for most parameters (niche, notes, category, sender_identity details, spending_cap_cents). The description mentions 'verified sender identity' but does not clarify the sender_identity object's required fields beyond name and email.

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 saves PR outreach drafts as a job for review and send, and specifies return values (job_id + dashboard URL). It distinguishes from sibling tool 'draft_pr_outreach_for_contacts' by focusing on queuing rather than drafting.

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?

It explicitly requires ECHO_API_KEY and describes key behaviors (verified sender, caps, suppression list, reply routing). However, it does not explicitly state when to use this tool versus alternatives like 'draft_pr_outreach_for_contacts' or when not to use it.

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