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

readOnlyHint=true already tells the agent this is a safe read. The description goes beyond that by enumerating the returned content (sender, subject, message, delay) and pinning the underlying endpoint, which is real value given there is no output schema. Auth requirements and pagination are still unstated.

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, zero filler. The resource and its scope come first, and the endpoint mapping is tucked at the end as supporting detail.

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 single-parameter read tool with annotations covering safety, the description pairs the resource definition with the shape of the returned emails, compensating for the missing output schema. Only auth/pagination behavior is left silent, a minor gap at this complexity.

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?

Only one parameter, form_id, and schema description coverage is 100%, so the schema fully documents it. The description reinforces the formId placement via the endpoint path but adds no format or constraint detail beyond the schema's type and bounds. 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?

Specific verb (list) plus resource (a form's confirmation emails) and a definition of what those emails are — the ones sent to the submitter. That semantic definition implicitly separates it from the sibling formstack_list_notification_emails (admin-facing notifications), though the alternative is never named.

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 by the resource definition: use it when you need a form's auto-reply confirmations. There is no explicit when-to-use, no when-not, and no pointer to formstack_list_notification_emails for the other email type, which is the most likely confusion.

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