get_outreach_template

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

No annotations are provided, so the description carries the full burden. It describes the core function (returning a template) but does not disclose behavioral traits such as idempotency, side effects (none expected), or access restrictions. The description is honest but lacks depth beyond the purpose.

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 a single sentence of 30 words, front-loaded with the key action. Every part adds value: the verb, resource, scope (country/channel specific), and examples. No unnecessary words or fluff.

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 the tool has only 2 parameters with enums and no output schema, the description covers the core purpose and parameter rationale. It does not explicitly state the return format (e.g., text content), but that is inferable. Compared to siblings, it stands alone as a focused retrieval tool; however, a brief note on output would improve 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 coverage is 0%, meaning the description must compensate. It adds meaningful context by explaining why country and channel matter (e.g., country calibrates formality, channel determines type like cold_email vs breakup). This goes beyond the enum lists in the schema, helping the agent understand parameter significance.

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 verb 'Get' and identifies the resource as a 'country-specific, channel-specific outreach template', making the purpose immediately obvious. It also provides specific examples of channel types (cold email, LinkedIn DM, etc.) and calibration details (formal address for Germany, French for France), which distinguish it from generic template tools.

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 for obtaining localized outreach templates but does not provide explicit guidance on when to use this tool versus the sibling tools (e.g., get_followup_cadence, get_full_emea_pack). There are no when-not-to-use directives or alternative recommendations, leaving the agent to infer context.

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