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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond them: it doesn't say whether templates are built-in defaults or project/site-specific custom templates, nor whether the result is scoped or paginated.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity comes at the cost of under-specification rather than being genuinely complete.

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?

With no output schema, 0% parameter coverage, and no explanation of what a template contains or how project/site scoping affects results, the description leaves real gaps for a two-required-parameter list tool. An agent can invoke it but cannot predict what it returns or when it is the right choice.

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 0% for two required parameters (projectId, siteId), and the description never mentions them, so an agent gets no signal about why both a project and a site scope are required or how they interact. The description does not compensate for the coverage gap.

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 states a verb ("List") and a resource ("email templates available for outreach"), so the basic operation is clear. However, it is essentially a paraphrase of the tool name/title with the word "email" added, and it draws no distinction from nearby siblings such as list_outreach_threads, list_outreach_keywords, or get_outreach_draft_options.

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?

There is no guidance on when to call this versus alternatives — not even a mention that it belongs to the outreach-automation family alongside list_outreach_threads or get_outreach_automation_policy. No prerequisites or exclusions are stated.

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