list_emails

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

With no annotations provided, the description carries the burden of disclosing behavior. It mentions 'newest first' ordering and the available filters, which is useful. However, it does not disclose pagination behavior, return format, or whether it is a read-only operation, leaving gaps in full behavioral transparency.

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 concise and well-structured: two sentences with the main verb and object upfront, followed by filter capabilities. Every word contributes value, and it is easy to scan.

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?

Given the absence of an output schema and annotations, the description should explain what is returned, but it does not. It covers purpose, ordering, and filter options, which is good, but lacks details on pagination, default behavior, and return shape, making it only moderately complete.

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. The description enumerates several filter parameters (scope, status, tag, query, stream), but this largely mirrors the schema descriptions. It adds little beyond grouping them as filters, and omits page/per_page semantics, though those are well-described 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 clearly states the tool's function with a specific verb ('List') and resource ('messages of the CamelMailer server'), and specifies ordering ('newest first'). It distinguishes itself from siblings like get_email (single message retrieval) and list_templates/list_bounces (different resource types).

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 establishes the tool's purpose as listing and filtering messages, providing clear context for when to use it. However, it does not explicitly mention when not to use it or point to alternatives like get_email for individual messages, so it falls short of a full 5.

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