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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds real domain context beyond the annotations: which node types are legal in an email and which classes are forbidden (btn/card/shadow/gradient/absolute). That constrains how consumers can use the returned data.

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, front-loaded with the return contents, with the constraints packed into the second sentence. Dense but every clause carries information; no filler.

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, so the description must convey return shape, and it does (subject, preheader, node tree). The read-only nature and closed-world scope come from annotations. Missing only explicit pagination/error behavior, which is minor for a single-resource getter.

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 100%, with both id and the enum-constrained kind already documented, so the baseline is 3. The description's mention of {{variables.*}} and EmailSlot nodes is about content shape rather than parameter meaning, so it does not add per-parameter value.

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 and resource ('Read one site email') and enumerates the returned structure (subject, preheader, node tree, variables, EmailSlot nodes). 'One' implicitly separates it from the sibling list_site_emails, so an agent can distinguish the two without opening a schema.

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 only implied: reading a single email's structure is the natural prerequisite to preview_site_email or update_site_email, but neither is named and no when-not condition is given. The 'keep required slots exactly once' note hints at edit workflows but doesn't route the agent explicitly.

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