mc_listAutomationEmails

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

No annotations provided. The description only states 'list', implying a read operation, but does not disclose pagination, ordering, or the format of returned data (e.g., list of email IDs or full objects). No mention of potential side effects or constraints.

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 a very short phrase, which is concise and front-loaded. However, it is a sentence fragment and could be slightly more structured (e.g., 'Lists all emails in a given automation workflow').

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 list tool with one parameter and no output schema, the description is minimally adequate. It lacks information about the return type (e.g., array of email objects or IDs) and whether there are any limitations. Slightly more detail would improve completeness.

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 the single parameter workflowId already described. The tool description adds no new meaning beyond the schema, so it meets the baseline without improvement.

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 'List emails in automation workflow' clearly indicates the tool lists emails within a specific automation workflow, distinguishing it from sibling tools like mc_listAutomations (lists workflows) and mc_getAutomationEmail (single email). However, it does not explicitly state that it lists all emails for a given workflow.

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?

No guidance on when to use this tool versus alternatives. For instance, it does not mention that the workflowId is required or that this is for listing, while siblings like mc_getAutomationEmail retrieve a single email. The description lacks any context for usage decisions.

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