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

Annotations already declare readOnlyHint, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful content context (only Container/Text/Button/Image/EmailSlot and email-safe classes, no btn/card/shadow/gradient/absolute), but says nothing about errors, auth, or what happens if a slot is duplicated or missing.

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 sentences with the core action front-loaded and the structural constraints packed into the second. Dense but each clause carries real information; the parenthetical constraint is slightly awkward but earns its place.

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, the description carries the return-value burden and does list the returned elements plus the allowed node/class vocabulary. It stops short of explaining how the node tree is addressed for later edits, which a caller of add_nodes/update_site_email would likely need.

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% and both parameters are documented in the schema (including the 8-value kind enum sourced from list_site_emails). The description adds no format or constraint detail for id/kind, so the baseline 3 applies.

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?

Starts with a specific verb+resource ('Read one site email') and enumerates the payload it returns (subject, preheader, node tree, variables, EmailSlot nodes), which clearly separates it from list_site_emails, preview_site_email, and update_site_email.

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 an operational constraint ('keep required slots exactly once') but never states when to choose this over preview_site_email or update_site_email, nor the prerequisite 'id from list_site_emails' workflow end-to-end. Usage is implied by the word 'Read' rather than spelled out.

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