draft_outreach_for_event

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

With no annotations, the description carries the burden. It discloses the tool returns subject+body and is a demo, implying no sending or persistence. However, it doesn't mention any rate limits, authentication, or data handling, which would strengthen transparency.

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, no wasted words. First sentence states purpose and output format; second provides usage boundary. Efficient and front-loaded.

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 demo tool with moderate complexity (6 params, 3 required, no output schema), the description is nearly complete. It explains the purpose, output, and usage boundaries. Missing details on default tone or optional parameters like event_url slightly reduces completeness.

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 33% (only sender_pitch and recipient_role have descriptions). The description adds overall context (e.g., event_name is the event reference) but does not detail each parameter beyond the schema. Baseline 3 is appropriate.

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's specific action (generate a personalized cold email), the resource (referencing an event/community), and the output (subject + body). It distinguishes from siblings by mentioning it's a public demo and directing to an alternative for sending.

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?

Explicitly provides context: 'Public demo — for sending, deliverability, and reply triage, use Your Echo Agent.' This tells the agent when not to use this tool and what to use instead.

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