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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral value by stating that only names and IDs are returned, not full template content, and that both organization-level and event-level templates are included. It does not describe response format or pagination, but this is not a major gap given the simple read-only nature.

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 one short, front-loaded sentence with no filler. It communicates the action, scope, and output limitation efficiently.

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 simple two-parameter read-only tool with fully described schema and safety annotations, the description is largely complete. It conveys the output scope ('names and ids only'), which helps an agent decide whether this tool fits the need. It could mention return format or pagination, but those are minor for correct invocation.

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 input schema already fully documents the org and eventId parameters. The description's 'organization and event' phrasing loosely maps to these parameters but adds no additional semantic detail beyond what the schema already provides.

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 uses a specific verb ('List'), names the resource ('email templates'), and scopes it to 'organization and event'. It also explicitly limits the output to 'names and ids only', which distinguishes it from sibling tools like create_email_template, draft_email, and send_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?

The description implies read-only retrieval by saying 'List' and 'only', but it does not explicitly say when to use this tool versus alternatives like draft_email or send_email. There is no direct exclusion or alternative routing, leaving the usage context to be inferred.

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