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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful boundary that this does not create a draft or order, but it does not explain idempotency-key behavior or content-policy acknowledgement requirements.

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 tightly written sentences, front-loaded with the core action and immediately followed by the key exclusion. No wasted wording.

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?

This is an 11-parameter creation tool with very low schema description coverage and no output schema. The description explains the high-level purpose but leaves important required-parameter semantics and policy acknowledgement details under-specified for reliable invocation.

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 only 9%, so the description must carry most parameter meaning. It mentions text/Markdown, pages, style, paper, envelope, and sender, but omits required parameters like name, idempotency_key, and content_policy_acknowledged, as well as title and content_type.

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 uses a specific verb ('Save') and resource ('reusable letter') and explicitly scopes it with 'Does not create a draft or order.' That exclusion directly differentiates it from draft-creating siblings like create_draft and create_template_draft.

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 gives a clear when-to-use signal ('Save a reusable letter... with {{variable}} placeholders') and an explicit when-not ('Does not create a draft or order'). It stops short of naming the alternative sibling tools, so it is not a full 5.

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