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

Annotations already declare the operation as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful behavioral context by saying `get` returns subject, HTML, and text body, and that presets are available to copy when creating a new mailer. It does not discuss pagination, permissions, or error behavior, but those gaps are less critical given the annotations.

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 front-loaded with the core purpose, then uses a compact action list to explain dispatch behavior. Every sentence and bullet carries useful information with no wasted framing.

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?

Both supported actions, their required parameters, and the source of `event_id` are covered. Since an output schema exists and annotations define safety behavior, the description does not need to explain return structures or safety guarantees further.

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%, so the baseline is 3, but the description adds meaning to the `action` parameter by explaining what each enum value does. It also reiterates the UUID relationship for `event_id` and the conditional requirement of `template_id`, though much of that is already present 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?

The description states a specific verb and resource: reading email templates for an event. It also distinguishes the two supported actions, `get` and `list_email_template_presets`, with enough specificity that an agent can tell what each does without opening the 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?

It clearly tells the agent to dispatch via `action` and gives the purpose of each action: fetch one template versus list presets for copying into a new mailer. It also identifies `search_events` as the source of the required `event_id`. It does not explicitly compare this tool with sibling tools such as `read_mailers` or `update_email_template`, so it falls short of full alternative guidance.

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