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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lowered, yet the description still adds real value: validation behavior (unknown variables, missing/duplicate required slots, unsupported classes are rejected) and the fact that theme and company data are injected at send time rather than stored. It does not spell out partial-update semantics for unspecified fields, which matters for a destructive write.

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?

Three tight sentences with no filler, and the core action plus the reset alternative are front-loaded. Structure is good; density is high enough that a slightly clearer separation of write-vs-render would help, but nothing is wasted.

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?

No output schema exists, but the description covers the return path by pointing to preview_site_email for rendering the saved result. Given a destructive, idempotent 6-parameter mutation tool, the main remaining gap is what happens to fields the caller omits (implicit 'and/or' partial update), which is left to inference.

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 100%, so the baseline is 3. The description largely restates the schema's own fields (subject, preheader, nodes, reset) and adds only the validation angle, which is behavioral rather than parameter syntax; empty-string-equals-default is already in the schema.

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?

Specific verb+resource: 'Save a site email's subject, preheader and/or full flat node map, or reset: true' tells the agent exactly what is mutated and which fields are in play. It also names the downstream sibling preview_site_email, which helps separate saving from rendering, but it does not explicitly contrast with the read siblings get_site_email / list_site_emails.

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?

Usage is implied rather than stated: the agent gathers that this is the write counterpart to preview_site_email and get_site_email, and that reset:true restores defaults. There is no explicit 'use this when...' clause, no precondition (e.g. that id/kind must come from list_site_emails), and no exclusion of alternatives.

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