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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the source can be a campaign or a raw document, but says nothing about what happens on duplicate names, required permissions, or reversibility of a saved template.

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 sentence that front-loads the primary use case (saving an existing newsletter) and appends the secondary mode. Efficient with no filler, though the trailing 'or a full email document' is slightly loose.

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 creation tool with 5 params, a nested object, 40% schema coverage, and no output schema, the description resolves the main dual-mode ambiguity but omits return-value expectations and leaves several parameters unexplained.

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 40%, so the description should compensate. It reinforces the campaignId ('existing newsletter') and document ('full email document') semantics, but those already carry schema descriptions, and it adds nothing for name, category, or description.

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?

States a specific verb (saves) and resource (template) and clarifies that the source can be either an existing newsletter via campaignId or a full email document. This distinguishes it from create_newsletter (which makes newsletters) and update_email_template, though it doesn't explicitly name those siblings.

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 'or a full email document' clause implies the two supported input modes, giving some usage signal, but there is no explicit when-to-use guidance, no when-not, and no reference to alternatives like create_saved_reply or update_email_template.

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