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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation. The description adds useful partial-update semantics ('give only what changes') and draft-only scope, but the cryptic 'Free.' is unexplained and there is no mention of permissions, failure modes, or limits.

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 short and front-loaded, with the actionable scope stated immediately. The final 'Free.' is cryptic and arguably does not earn its place, but overall there is little wasted text.

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 4-parameter mutation tool with annotations but no output schema, the description covers the essential draft-only and partial-update behavior. It nevertheless omits what happens with non-draft issues, the role of issue_id, and the meaning of 'Free.', leaving clear gaps.

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?

The description names the three editable fields (subject, body, preheader) and signals that omitted fields are left unchanged, which maps to most parameters. With 50% schema description coverage, subject and preheader have no schema descriptions, but the description at least identifies them; issue_id is documented in the schema rather than the 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?

The description states a specific verb ('Change') and resource ('a draft's subject, body or preheader'), so an agent can tell it edits newsletter issue fields. It does not explicitly distinguish this from siblings like newsletters_write_issue or newsletters_send_issue, so it falls short of a 5.

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 phrase 'Give only what changes' implies partial-update usage for an existing draft, which gives some guidance. However, it never states when to use this instead of newsletters_write_issue or newsletters_send_issue, nor does it state exclusions such as already-sent issues.

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